resemble_list_investigation_runs

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the operation is a read/list and scoped to an agent, but does not mention pagination, ordering, recency limits, or whether the list includes failed/in-progress runs. For a list tool, these are meaningful behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence that is front-loaded with the action and resource. It is concise and readable, though it could add a bit more context without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a single required parameter and an output schema, so the description does not need to explain return values. However, with no annotations and no parameter guidance, the description is only minimally complete for an agent to call it correctly. It lacks guidance on how to find agent_uuid and what 'recent' means.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only mentions 'agent_uuid' implicitly via 'for a Detect Agent'. It does not explain the format of agent_uuid, how to obtain it, or any constraints. The description adds minimal meaning beyond the schema's bare property name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('List') and resource ('recent investigation runs') scoped to a Detect Agent. It distinguishes from siblings like resemble_get_investigation_run (which fetches a single run) and resemble_run_investigation (which starts one), though it does not explicitly name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context: listing recent runs for a specific agent. It does not explicitly state when to use this tool versus resemble_get_investigation_run or resemble_run_investigation, but the verb 'List' and 'recent' convey a browsing/history use case. No exclusions or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.