runs.get

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

Annotations already declare readOnly, non-destructive, idempotent. Description adds valuable behavioral context: read-only DB query, no external calls, no credit consumed, 'safe to poll', and partial results if status is 'running'.

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?

All sentences are relevant and front-loaded. Slightly verbose with repeated mentions of 'outreach.plan or outreach.draft' and 'leads.find', but still 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?

No output schema, but description fully explains return structure: run_id, status, idea text, results array with field details, and metadata. Covers all necessary information for the agent.

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 coverage is 100% with run_id description already clear. Description adds meaning by specifying the source of run_id (from leads.find) and giving example format 'run_abc123', plus contextualizing its usage.

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?

Clear verb 'Fetch the full result' and resource 'previously-started run by its run_id'. Distinguishes from siblings by mentioning runs.list for finding run_ids and leads.find for starting runs.

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?

Explicit when-to-use scenarios: re-analyse earlier run without spending credit, hand leads to outreach.draft/plan, poll long-running job. Also states what NOT to do: 'Do NOT call this without an existing run_id; use runs.list first.'

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