Quarterback

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

No annotations exist to contradict, but description adds minimal behavioral context beyond 'Get'—omitting how prioritization is calculated, side effects, or return format.

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?

Single sentence avoids bloat, but extreme brevity leaves critical gaps; not structured to front-load key distinctions from 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 tool's complexity (4 parameters, 2 enums) and crowded sibling namespace; lacks output guidance or prioritization logic explanation.

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 has 0% description coverage and description fails to compensate, mentioning none of the four parameters (timeframe, project_name, status, limit) or their interactions.

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?

Restates tool name tautologically ('get_priorities' → 'Get prioritized list') and fails to distinguish from siblings like get_quick_wins, get_blocking_tasks, or get_agent_ready_tasks.

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 sibling task-querying tools or what constitutes 'organizational context'.

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