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

Annotations include idempotentHint=truecker, destructiveHint=false, and readOnlyHint=false, indicating a safe, non-mutating operation, which the description does not contradict. Since no annotations are provided for behavior like rate limits or data sensitivity, the description adds the instruction to include conversation data, which hints at the need for context. However, it does not disclose what happens after submission (e.g., no confirmation), but given the safety profile, a baseline of 3 is fair.

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 concise: two sentences that cover the main purpose and a critical usage detail. It is front-loaded with the action, and every word earns its place. No fluff or redundancy.

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 feedback tool with 3 parameters, a required field, and no output schema, the description provides essential guidance (include conversation array) and clear purpose. The absence of output schema is acceptable since the tool likely reports success/failure. The description is sufficient for an agent to use the tool correctly for reporting bugs/feedback, so a 4 is justified.

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%, meaning the schema provides only parameter names and types, with no additional meaning. The description mentions the 'conversation' parameter (the conversation array) and its importance, adding some semantics beyond the schema. However, it does not explain the 'context' parameter or the format of 'conversation' beyond being a string (likely JSON). With 0% coverage, the description should compensate more, but it does partially, so a 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 clearly states the tool's purpose: to report bugs, missing features, or send feedback. It also specifies a key requirement (include the conversation array) for reproduction, which adds value beyond the name. However, it does not explicitly distinguish itself from the sibling tool 'show_version' or other potential feedback channels, but given the sibling list, none are directly similar, so a 4 is appropriate.

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 the tool (when reporting bugs/feedback) and gives a critical instruction (include conversation array). It does not explicitly state when not to use it or mention alternatives, but the context is fairly clear from the purpose. This is adequate but lacks explicit exclusions or alternative guidance, so a 3 is suitable.

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