get_runs

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

Beyond the readOnlyHint annotation, the description warns that each run is large and can flood context, advising small limits. This adds behavioral insight about resource usage and potential performance impact.

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?

Highly concise and well-structured: one-line purpose, a brief behavioral note, then a clear Args list with examples. Every sentence adds value, no redundancy.

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 the tool's complexity (4 parameters, output schema exists), the description covers all necessary aspects: what is retrieved, how to limit and paginate, ordering syntax, and usage examples. The output schema handles return values, making this complete for agent use.

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 parameters have 0% description coverage, but the description explains each parameter in detail: experiment_id is the ID, limit is max with small limit advice, offset for pagination, and order_by with formatting examples including backticks for special characters. This fully compensates for the schema gap.

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 clearly states 'Get runs for a specific experiment with full details,' specifying the verb, resource, and scope. It distinguishes from siblings like 'get_run' (single run) and 'query_runs' (complex queries) by focusing on a specific experiment and full detail retrieval.

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 explicit guidance on limiting results (3-10) to avoid context flooding and using offset for pagination. Includes examples for typical usage. Does not directly compare to sibling tools but implies appropriate use cases.

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