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

Annotations declare readOnlyHint=false and idempotentHint=true, so mutation and repeat-safety are already covered. The description adds useful semantics for the issue field and notes optionality of two params, but doesn't state permission requirements or the effect of sending feedback on downstream data. This is adequate additional context but not rich.

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?

Compact and front-loaded, opening with the core purpose before parameter notes. The long enumeration of issue values is necessary for semantics but contributes to density. No filler sentences.

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 an output schema exists, return values need not be described. With zero schema description coverage, the description supplies the missing parameter semantics and links to the ask tool. It is nearly complete, lacking only any note on permissions or consequences of submitting feedback.

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 0%, so the description must compensate. It explains request_id refers to a prior « ask » response id, useful is true/false, and enumerates all seven issue enum values with glosses, plus optionality of issue and comment. This meaningfully adds to the bare schema, though comment could be slightly more specific.

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 states a specific action tied to a specific upstream tool: telling whether a response obtained with « ask » was useful. It clearly connects to its sibling ask and is distinguishable from calculate. It does not explicitly name a verb like 'submit feedback', but the intent is unambiguous.

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 clarifies this operates on responses from a specific sibling tool (« ask ») and requires the request_id from that response. It does not discuss timing or when not to send feedback, but the contextual link to ask is strong guidance for invocation.

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