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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses genuinely useful behavior: no auth required, that counts by kind become public on the roadmap while messages stay private, and that sensitive data must never be included. This data-handling and visibility disclosure is real added value, though it says nothing about what a call returns or error behavior.

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?

A single tight paragraph: purpose first, then prerequisites, then data-handling caveats. Every sentence carries weight, with only mild redundancy between the enumerated kinds and the chained clauses.

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 4-parameter, one-required submission tool with no output schema, the description covers purpose, prerequisites, acceptable inputs, and privacy constraints. It leaves a small gap on what happens after submission (confirmation/return), but otherwise the agent has enough to call it correctly.

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 75% with self-documenting enum values for 'kind', and the description's category list maps closely to that enum without adding much beyond it. The note/about/contact parameters are explained in the schema itself, so the description neither compensates nor detracts; baseline 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 opening clause states a specific action (submit feedback) and enumerates exactly what qualifies: missing services, metrics, features, wrong data, unclear docs. This is clearly a write/submission tool and cannot be confused with its read-only siblings (get_*, search_services). It stops short of explicitly naming any sibling, so it lands at 4 rather than 5.

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?

'No key needed' and 'we use it to decide where to look next' tell the agent the context and prerequisites for calling it. The list of acceptable feedback kinds implicitly bounds when to use it, but no alternative or when-not-to-use guidance is given.

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