search-runs

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

Lacks annotations and the description is too brief to disclose behavioral traits. For a tool with 7 parameters and no annotations, important details like filter syntax, pagination mechanics, and return format are missing.

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?

Single sentence is concise and front-loaded with verb and resource. It communicates the core purpose efficiently, though it could benefit from moderate expansion to cover key behavioral details.

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?

Given no output schema and no annotations, the description is incomplete. Fails to mention return format, pagination details, or filtering capabilities, leaving significant gaps for a complex search tool.

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 71%, so the schema provides decent parameter documentation. However, the description adds no extra meaning beyond what the schema already states, resulting in no added value for parameter understanding.

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?

Description clearly states verb 'search' and resource 'runs', and adds key features 'filter expression' and 'pagination'. It implies a generic search capability but does not explicitly differentiate from siblings like 'search-runs-by-tags', which is a minor gap.

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?

Provides no guidance on when to use this tool versus alternatives. With many sibling search tools (e.g., search-runs-by-tags), the absence of usage context forces agents to rely on tool names alone.

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