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

With no annotations provided, the description carries the full burden and discloses key behaviors: creates a GitHub issue on a public repo (cross-machine visible), stores locally, and requires gh CLI authentication. It could mention if there are any rate limits or side effects like notification triggers, but overall sufficiently transparent for a feedback tool.

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?

Every sentence earns its place: a clear purpose, a 'WHEN TO USE' section, and behavioral notes. No filler, and the structure is front-loaded for quick scanning.

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 output schema exists (so return values are covered) and the tool's purpose is straightforward, the description covers all essential aspects: purpose, usage scenarios, side effects, and prerequisites (gh CLI). No gaps.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the parameter names and types; it lists feedback_type, subject, body, reporter, repo_path but offers no additional context like allowed values or formatting tips.

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 'Report friction/bugs/enhancements to the nucleus team' with a specific verb and resource, and the sibling tools are all other nucleus operations, none of which overlap with feedback functionality.

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?

Explicitly provides 'WHEN TO USE:' with concrete scenarios like lane misbehaves, task fails, confusing SPEC.md, or improvement idea, giving clear context for when to invoke this tool.

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