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

Annotations already disclose the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds one genuinely new behavioral fact — "A human reads every submission" — telling the agent there is no automated response. It does not say whether feedback is publicly visible, whether contact is required for a reply, or anything about rate limits.

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, front-loaded with the action and recipient, with the reassuring "human reads every submission" placed last. Every clause carries information; nothing is redundant.

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 simple one-required-parameter submission tool with no output schema, this covers purpose, eligible content, and audience. The main gap is that it does not tell the agent what happens after sending (confirmation, ticket, follow-up) or whether contact is needed for a reply.

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 75% and the schema already explains model, contact, and message (including the 5000-char limit). The description's topic list loosely maps to the category enum values (bugs, docs, pricing, model requests) but adds no format or syntax detail beyond the schema, so the 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?

The description gives a specific verb and recipient ("Tell the Open Uncensored team") and enumerates the exact subject matter it accepts — "missing models, bugs, pricing, docs, anything that got in your way." Nothing about it could be confused with siblings such as chat, get_guide, or buy_credits.

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?

The list of eligible topics implies when to reach for this tool, but it never states exclusions or alternatives (e.g., "use chat for immediate answers, use get_guide for documentation"). Usage is inferable rather than stated.

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