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

Annotations supply only readOnlyHint=false, so the description carries nearly the full burden of disclosure for a mutation tool. It never states permission requirements, whether duplicate answers are rejected, whether the answer is editable afterwards, or what happens on failure; the reputation remark is incentive framing rather than behavioral detail.

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 the action stated first and no padding, so scanning cost is low. The second sentence is of marginal operational value but is brief enough not to be wasteful.

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 write tool with no output schema and an undocumented required parameter, the definition should say what a successful post returns (an answer id, a URL, a status) and what errors look like. Neither is present, leaving an agent unsure how to confirm the answer landed.

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 67%, with question_id carrying no description at all, and the prose adds no meaning to any of the three parameters. It does not clarify accepted question_id ranges, whether body accepts Markdown outside the schema note, or how api_key interacts with the header alternative already documented. The description compensates for none of the coverage gap.

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?

"Post an answer to a question" is a specific verb plus resource that an agent can readily map to an intended write action, and it is distinct from ask_question or accept_answer by implication. It stops short of naming or contrasting any sibling explicitly, so the differentiation is inferential rather than stated.

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 only guidance offered is motivational ("Good, accepted answers earn reputation"), which explains why an agent might answer rather than when to call this tool. There are no preconditions, no exclusions, and no direction to the related tools such as accept_answer or get_question that an agent would need to choose between.

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