backlog

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

Good: No annotations provided, so description carries full burden. Discloses return payload details ('all fields including annotations, dependencies, docs, and computed urgency') which compensates partially for missing output schema. Could improve by explicitly stating this is read-only/safe or noting error behavior.

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?

Excellent: Three sentences with zero waste. Front-loaded with the core action ('Get the full JSON details'), followed by return value specifics, usage guidance, and sibling alternative. Perfect information density.

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?

Good: For a simple single-parameter read tool without annotations or output schema, the description adequately explains the return payload (field enumeration). Sufficiently complete given the tool's limited complexity and rich parameter schema.

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?

Adequate: Schema coverage is 100% with complete parameter documentation. Description mentions 'ID or UUID' which aligns with schema but adds no additional semantic context (format specifics, validation rules) beyond what the schema already provides. Baseline 3 appropriate when schema does heavy lifting.

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?

Excellent: Specific verb 'Get' with resource 'task' and scope 'single task by ID or UUID'. Explicitly distinguishes from sibling 'task_list' by contrasting single vs multiple task retrieval.

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?

Excellent: Explicit when-to-use ('when you need complete details for one specific task') and clear alternative ('For querying multiple tasks, use task_list with a filter instead'), providing clear selection criteria against siblings.

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