Quick report (no key)

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

Goes well beyond the annotations: it discloses that keyless reports are anonymous, filed under a shared anon-xxxxxx account, shown as 'unverified', and do not move the score; that notes are locally scanned for personal data; and that handle+signature yields an API key in the same call. These are exactly the consequences an agent cannot infer from readOnlyHint=false / destructiveHint=false / openWorldHint=true.

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?

Dense but nearly every clause carries actionable information, and the key framing (no key needed, failures welcome) is front-loaded. It is one long semicolon-chained paragraph, so the anonymity and rate-limit rules take effort to locate; light structuring would improve it.

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 10-parameter mutation tool with no output schema and no explicit return-value documentation, the description covers attribution, anonymity consequences, rate limiting, privacy screening, synonym normalization and in-call key provisioning. An agent can call this correctly without guessing.

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 100%, so the baseline is 3; the description still adds value by explaining the handle+signature pairing to mint a key, that model/client/tool_versions surface as 'Tested on', that client falls back to initialize clientInfo, and that common outcome words like 'worked'/'failed' are accepted despite the strict enum. The api_key format is left to the schema, but the env-var preference is restated usefully.

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?

It states a specific verb and resource: leave the outcome of a recipe you tried, in one call, without download or registration. The anonymous-vs-attributed distinction clarifies scope well, but the description never distinguishes itself from the sibling `report_result`, which sounds functionally overlapping.

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?

Clear context for when to use it ('Tried a recipe? Leave its outcome') plus explicit encouragement to report failures and an explicit constraint of one report per recipe per source per 24 h. It gives no exclusion or comparison against `report_result`, so it stops short of full when/when-not guidance.

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