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

Annotations only declare mutation and idempotency; the description adds substantial behavior beyond them: marker/placeholder conventions, the '[confirm: …]' and unsourced-price rules, blocked-phrase failure saving nothing, no tables, content-check failure modes, refusal conditions, and an expected latency ('up to a minute'). The 'returns it and writes nothing' clause concretely explains the idempotentHint.

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 behavior is front-loaded and almost every clause carries information, but the middle section is a dense run of semicolon-linked rules with nested parentheticals that take effort to parse. Given the tool's complexity the length is defensible, but it is not maximally scannable.

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?

With an output schema present, return values need no explanation, and the description covers everything else an agent needs: side effects, idempotent behavior, refusal cases, failure modes, follow-up tools, and timing. Nothing material is missing.

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 would be 3, but the description goes further by explaining what each enum value means (vs = '<you> vs <them>', alternative, pricing = what they charge and how you compare) and confirms competitorId comes from list_competitors. This adds real semantics beyond the bare enum list.

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 opening sentence gives a specific verb, resource, and output artifact: 'Drafts a comparison page for one tracked competitor as a competitor_page draft post,' then enumerates the three kinds with their meaning. An agent can distinguish this from list_competitors or check_draft without opening either schema.

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?

It states preconditions (competitor must be tracked/existing; refusal for unknown, untracked, or content-excluded competitors), a when-not path (if a live post of that kind exists, it returns it and writes nothing), and the next step (never submits – fix checks, then call submit_post). It also names related tools, including list_competitors as the source of competitorId.

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