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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the safety basics are covered. The description adds genuine value by disclosing that submissions are private and that a receipt is returned, but it says nothing about what happens to the complaint afterward, review timelines, or whether it can be withdrawn.

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 short sentences with zero filler, and the core action is front-loaded before the return-value note. Nothing is repeated from the schema or annotations.

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 six-parameter, mostly-required mutation tool with 0% schema documentation and no output schema, the description is far too thin. It omits parameter meanings, accepted values for target_type/category, what the receipt contains, and what the privacy guarantee concretely means.

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 six parameters, so the description carries the burden and largely fails: only 'good-faith' gestures at good_faith and 'without a participant key' implies no key argument. target_type, target_id, category, explanation, and contact — including the valid values for target_type and category — are completely undocumented.

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 states a specific verb and resource ('Submit a ... complaint') and scopes it as private and good-faith, so the agent knows this is a reporting action rather than a read. It does not differentiate itself from the sibling 'report_status', which also sounds like a reporting tool, so it stops short of a 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?

'without a participant key' implies the usage context: use this when no authenticated participant credential is available. However, there is no explicit when-not guidance, no mention of the alternative 'report_status', and no prerequisites or follow-up steps, leaving usage mostly inferred.

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