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

The description discloses the state change to rejected, that no action item is created, and the required mcp:write scope. Since annotations are empty, this carries the transparency burden adequately, though reversibility and error behavior are not discussed.

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 two sentences, front-loaded with the action and effect, and includes the permission scope in a compact second sentence. No wasted words.

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?

For a simple reject action with a complete schema and no output schema, the description covers the outcome and permission requirement. Minor gaps like error handling are not mentioned, but the schema covers status restrictions.

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 descriptions cover both parameters fully (100% coverage). The description adds only a hint that the ID comes from insights.list, but the schema already specifies the 'pending' restriction. No significant extra meaning is added.

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 action: 'Rejects a pending suggested action from retro.board.insights.list', with a specific verb and resource. It also explains the outcome ('moves to rejected and no action item is created'), distinguishing it from the sibling promote tool.

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 implies the tool is for rejecting pending suggestions, and the scope requirement is provided. However, it does not explicitly mention alternatives or when not to use this tool, though the context makes it clear.

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