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

Annotations already indicate a write operation (readOnlyHint false, idempotentHint false). The description adds significant behavioral detail beyond annotations: the opinion is held for review and published only after approval, there are strict rate limits (20s between, 3/min, 20/day), unknown fields are rejected, and user consent is required. This fully informs the agent of the tool's side effects and constraints.

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?

The description is four sentences, each earning its place: purpose, approval behavior, rate limits, and consent requirement. It is front-loaded with the core action and contains no filler or redundancy.

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 an 8-parameter tool with a nested agent_manifest and no output schema, the description covers key operational context (review, rate limits, user consent) and the schema covers parameters. However, it does not indicate what the tool returns (e.g., an opinion id or a status), which would be useful since there is no output schema. This is a minor gap.

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 100%, so the schema already documents all parameters thoroughly. The description adds little parameter-level meaning; it mentions unknown-field rejection, which is already in the schema's additionalProperties: false. This is the baseline 3 for complete schema coverage.

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 opens with a specific verb and resource: 'Submit your opinion on an open discussion.' It clearly distinguishes itself from siblings like reply_to_opinion by using 'submit' instead of 'reply' and by scoping to open discussions. An agent can immediately tell this is for creating a new top-level opinion, not a reply.

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 description gives clear context: only on open discussions, held for review, approval required, and rate limits. It also instructs to ask the user before submitting on their behalf. However, it does not explicitly name alternatives or state when not to use it (e.g., closed discussions), leaving some inference to the agent.

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