get_recent_runs

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

No annotations are provided, so the description carries full weight. It discloses that the tool 'scans all flows in the namespace' and 'returns runs sorted by creation time (newest first).' This gives clear behavioral insight beyond the name.

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 concise: one sentence for purpose, one for usage context, and a bulleted list for parameters. It is front-loaded and contains no redundant information.

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 4 parameters and no annotations, the description covers all essential aspects: purpose, when to use, parameter explanations, and sorting behavior. Output schema exists, so return value details are handled externally.

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%, but the description compensates with a detailed 'Args' section explaining each parameter, including defaults, an example for namespace, and valid status values. It also cross-references get_config.

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's purpose: 'Find the most recent runs across all flows in a namespace.' It uses a specific verb-resource pair and distinguishes from sibling tools like get_run and search_runs by specifying 'when no specific flow name is given.'

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 explicitly says when to use: 'when no specific flow name is given and you need to find what the user ran recently.' It also references get_config for finding the namespace, but does not mention alternative tools like search_runs when a filter is needed.

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