runs.list

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

Discloses read-only DB query, user-scoped, no external calls, no credit consumed, idempotent. Annotations already cover readOnlyHint and idempotentHint, but the description adds context on scope and credit consumption, which is helpful but not essential.

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?

Concise and well-structured: front-loaded with main functionality, then behavior, usage guidance, and return format. Every sentence adds value with no filler.

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 parameters and no output schema, the description fully covers the tool's purpose, behavior, usage context, and return format (fields, ordering). No gaps.

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?

No parameters in schema (100% coverage). Description doesn't need to add parameter details; baseline 4 for zero parameters.

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?

Clearly states the tool lists the user's recent lead-generation runs with specific constraints: newest first, capped at 50. Distinguishes from siblings like runs.get and leads.find by specifying the resource and scope.

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 when-to-use scenarios (revisit previous hunt, get run_id, confirm completion) and a when-not-to-use (enumerate other users' runs). Names alternative tools like runs.get and outreach.plan.

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