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

With annotations only declaring readOnlyHint=false, destructiveHint=false, openWorldHint=false, the description carries real extra value: it specifies rejection-without-persist for secret-bearing, oversize, or malformed payloads, optional authentication with anonymous rate limiting, zero credit cost, and that the result is a receipt rather than analysis. These operational traits are not derivable from the annotations or schema.

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?

Roughly five sentences, each carrying distinct information (payload shape, return value, triage ownership, rejection policy, auth/cost). Front-loaded with the core action, though the trailing 'not investment advice' clause is marginally tangential.

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 mutation tool with nested params and an output schema, everything an agent needs is present: payload shape, return value, auth/rate-limit behavior, failure modes, cost, and downstream disposition. Return-value details are rightly delegated to the existing output schema.

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% across 8 params, so the description must compensate — and it does, enumerating category, message, and every optional field (URL, route, tool, request ID, trace ID, reproducible context). It stops short of clarifying per-field constraints such as message length or the context sub-object's ticker/fiscal_year/executive_id fields, so it is strong but not exhaustive.

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 ('Accepts') and resource ('structured product-feedback report'), plus an enumerable payload (category, message, optional URL/route/tool/request ID/trace ID/context) and the returned artifact (opaque report ID). This cleanly separates it from the read-only siblings (get_claim_evidence, get_company_dossier, etc.) without needing their schemas.

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?

Usage context is clear: this is the submission path for product feedback, costs 0 credits, and disposition is owned by human triage. It does not explicitly name a when-not or an alternative sibling, but none exists for a write/feedback tool in this toolset, so the guidance is adequate rather than exhaustive.

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