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

Annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description does not contradict these. It adds context that the tool expects a conversation array for reproduction, which is useful. However, it doesn't describe what happens after reporting (e.g., does it create a ticket? Does it notify developers? What is the response?). For a read/write operation (since readOnlyHint=false), it could benefit from stating if the message is stored or sent externally. Since annotations exist, the description's additional context about conversation is helpful but insufficient for full transparency.

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 one sentence (with two clauses) and zero waste. It front-loads the purpose ('Report a bug...') and then gives a specific usage hint. Perfectly concise and well-structured.

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 3 parameters (1 required), no output schema, and annotations are present. The description explains the core purpose and the conversation parameter's role, but it lacks information about expected output or response, any limitations (e.g., maximum size of message/conversation), and whether it's a fire-and-forget. Given the tool's simplicity, it's adequate but not comprehensive. The description could mention that the tool is for user feedback and not for diagnostic queries, but it's somewhat complete for its purpose.

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?

The input schema has 3 parameters, but description coverage is 0% (the schema has no descriptions for context, message, or conversation). The description itself explains that 'message' is the report content, 'conversation' is a stringified JSON array for reproduction, and 'context' is a default empty string (likely for additional context). The description's instruction to 'Include the conversation array with recent messages' clarifies the purpose of the conversation parameter beyond the schema's basic types. Since schema coverage is 0%, the description must compensate, and it does for 'message' and 'conversation', though it doesn't explicitly mention 'context' (though 'context' might be implied by the name). Overall, it adds significant meaning over the schema.

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's purpose: 'Report a bug, missing feature, or send feedback.' It identifies the primary actions (reporting and sending) and the target (bug/missing feature/feedback). This distinguishes it from sibling tools like 'poupa_add_transaction' or 'marketplace' which have different purposes. However, it doesn't explicitly differentiate from a potential generic 'feedback' tool, but given the sibling list, it's reasonably distinct.

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 when to use this tool (when reporting a bug, missing feature, or feedback) and even suggests including conversation context ('Include the conversation array with recent messages for reproduction'). However, it does not explicitly state when NOT to use it or mention alternatives. For instance, it doesn't say 'for transaction issues, use poupa_* tools' or similar. The guidance is clear enough for a feedback tool, but lacks exclusions or comparisons.

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