backlog_capture_requirement

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., side effects, authorization needs, or data persistence). The phrase 'recording' implies creation, but the tool could also update existing requirements, which is unclear.

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?

The description is a single sentence, making it efficient but vague. It earns its place by being brief, but lacks sufficient detail for a 15-parameter tool.

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 the tool's complexity (15 parameters, no output schema, no annotations), the description fails to explain return values, behavior, or how parameters interact. The phrase 'current project' is ambiguous without defined scope.

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?

With only 7% schema description coverage, the description adds no parameter context beyond the schema's minimal descriptions. An agent cannot infer which of the 15 parameters are key or how they relate (e.g., 'as', 'date', 'status').

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?

The description clearly states the tool records a 'human or system requirement' in the current project, providing a specific verb and resource. However, it does not differentiate from sibling tools like backlog_capture_prompt or backlog_capture_reference.

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?

The description only says 'use when recording...' with no guidance on when not to use, prerequisites, or alternatives. This leaves an AI agent without context for tool selection.

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