aiworkhub_dashboard_needfix_capture

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

With no annotations, the description carries the full disclosure burden and does well: it says a write gate is required, that kind synonyms are normalized, that either a new or deduplicated row is persisted, and that a capture receipt is returned. It still leaves the deduplication criteria implicit, which is the main remaining behavioral gap.

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 core operation is front-loaded in the first sentence, followed by usage guidance and behavioral details. Every sentence adds useful information without repetition or padding.

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?

The tool has an output schema, so it need not explain the receipt format, and the schema fully documents parameters. The description covers the write gate, deduplication behavior, and sibling alternatives, leaving only the precise deduplication rule unspecified.

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 description coverage is 100%, so the schema already explains all seven parameters, including kind normalization, severity levels, truncation limits, and include_item. The description adds only the normalization/deduplication context, so baseline 3 is appropriate.

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 gives a specific verb and resource: capture a new NeedFix item or deduplicate against an existing live row. It also explicitly distinguishes this tool from aiworkhub_dashboard_needfix_update and aiworkhub_dashboard_needfix_transition, so an agent can select it without inspecting the schema.

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?

It states exactly when to use this tool: to record a new bug or proposal in the NeedFix inbox. It names the sibling alternatives for editing and status changes, and adds the prerequisite that an open write gate is required.

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