get_runs

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

With no annotations available, the description bears full responsibility for disclosing behavioral traits. It fails to mention what happens if the para_id is invalid, whether the tool is read-only, or any side effects. The description is too brief to convey transparency.

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?

The description is extremely concise, fitting in two sentences. It front-loads the purpose effectively. However, it could benefit from structured formatting to improve readability, but remains efficient.

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?

Despite having an output schema, the description does not explain the return format or list the formatting properties returned. Given the tool's specific function and many siblings, more context is needed to fully understand its usage.

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?

The description adds 'paraId of the target paragraph' to the para_id parameter, which is not present in the input schema (coverage 0%). However, it does not explain how to obtain a valid paraId or provide examples, so the added value is limited.

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 the tool retrieves all runs in a paragraph along with their formatting properties. It identifies a specific resource ('runs') and action ('get'), distinguishing it from sibling tools like get_paragraph or get_paragraph_format.

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?

No guidance is provided on when to use this tool versus alternatives like get_paragraph or get_tracked_changes. There is no mention of prerequisites or scenarios where this tool is appropriate.

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