Quarterback

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

Discloses the selection criteria (high impact, low effort) but omits output format, side effects, or whether results are ranked; no annotations provided to supplement this.

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?

Extremely concise single sentence with no fluff, though arguably too brief for the tool's contextual complexity given numerous siblings.

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?

Insufficient for the task management domain complexity; missing output schema description, differentiation from 5+ sibling retrieval tools, and parameter details.

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?

Adds no parameter context despite 0% schema description coverage; fails to clarify that project_name scopes the search or that limit defaults to 5.

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 defines 'quick wins' as high impact, low effort tasks, but doesn't clarify if it filters existing tasks or generates suggestions, nor how it differs from siblings like assess_task_value or get_priorities.

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 no guidance on when to use this versus alternatives like get_priorities or get_agent_ready_tasks, nor when-not-to-use scenarios.

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