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

Annotations only give the mutation/open-world safety profile, and the description goes well beyond: it states the answer goes live publicly and immediately, that images must be supplied as URLs, that a per-call confirmation is on by default, and that the user's Cotlet API key with app access is required. Immediacy, publicity, and auth needs are exactly the kind of context that earns credit beyond annotations.

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 front-loaded verb+resource is good, but the opening repeats itself ('Publish an answer as you under a question. Publishes an answer under your name below the question you name'), and the confirmation point is stated twice. Roughly half the sentences earn their place, the rest restate.

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 public social-post mutation with no output schema but with annotations present, the description supplies the missing behavioral essentials: publication immediacy, public reach, credential needs, and that confirmation is expected. Nothing critical for calling it correctly is absent, though the dangling confirmation phrasing could be tightened.

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 both parameters (question_url, body_markdown) are already documented. The description adds only a small hint ('Images go in the body as URLs') that partially overlaps with the schema's own note, so baseline 3 is appropriate.

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 names a specific verb and resource ('Publish an answer ... under a question') and clarifies the answer is authored under the user's name, which an agent can distinguish from quora_ask_question or quora_post_to_space. It stops short of explicitly naming the sibling it differs from, so it's clear but not fully differentiated.

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 gives real context ('Reaches other people: confirm with the user before each call') and notes the confirmation default can be turned off, which is usable guidance. However, it never names an alternative tool or states when NOT to use it, so usage is implied rather than explicit.

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