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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes well beyond that by disclosing that it relays comments verbatim and never embellishes, that it is rate-limited per user, and that no paid entitlement is needed. Those are the exact constraints an agent needs before calling a mutating tool on a user's behalf.

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?

Two tight sentences with the action front-loaded and behavioral caveats (verbatim relay, rate limit, entitlement) packed efficiently. No filler or repetition of the title.

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?

An output schema exists, so return values need no explanation. For a 4-param mutation tool with a nullable optional linkage, the description covers authentication ("authenticated user"), verbatim handling, rate limits, and entitlement — everything needed 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 description coverage is 100%, so the schema already documents run_id, comment, category, and listing_id. The description reinforces the verbatim-comment and category semantics but adds no syntax, format, or linkage detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource ("Email the NeverApply team feedback") and enumerates the exact categories of feedback accepted. No sibling tool overlaps with this action, so no differentiation is required, and the agent can tell instantly what it does.

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?

Gives clear context for use: bugs, bad listing data, match-quality complaints, feature requests, support questions. It does not state when NOT to use it or point to an alternative route (e.g. a support link), but the usage context is unambiguous.

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