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

Going well beyond the annotations, it discloses privacy (private feedback), auth requirements (no registration needed), strict content limits (enums and public record IDs only, never prompts or search text), and trust treatment (unverified, grants no points or permissions, does not establish distinct users). It also spells out idempotency semantics that differ by caller type: exact scoped replay for authenticated callers versus content-based dedupe within a UTC day for anonymous ones — consistent with idempotentHint=true rather than contradicting it.

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?

Most clauses earn their place — idempotency, privacy, and content restrictions are all decision-relevant — but the text is a dense, unstructured run of semicolon-chained caveats with mild redundancy between 'no registration required' and the anonymous-caller clauses. The purpose statement and the critical content restriction are buried mid-paragraph rather than front-loaded.

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 nested-input, no-output-schema write tool it covers behavior, privacy, trust effects, and dedupe semantics thoroughly, so no return-value explanation is needed. The one material hole is the undocumented category taxonomy, which an agent must know in order to submit a valid report.

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%, so the description carries the full burden. It explains idempotency_key behavior well and constrains record_ids to public IDs, but the 20-value 'category' enum (T01–T20) is never decoded, so an agent has no basis for choosing a value, and the nested 'input' object and its intent/reason/channel/acquisition fields are left entirely to the enum literals.

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 identifies the tool as 'optional private feedback after actual use', which conveys the resource but not precisely what is being reported — the name 'report_demand' and the opaque T01–T20 category enum leave the actual subject matter ambiguous. It also never distinguishes itself from near-siblings such as 'report', 'contribute', or 'suggest_research', so an agent cannot route on the strength of the description alone.

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?

'After actual use' and 'optional' imply the trigger condition, and the note that anonymous feedback 'does not trigger research or model work' hints that research-seeking callers should use another tool. However, no sibling is named as an alternative and no exclusion is stated explicitly, so routing remains inferential.

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