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

Annotations declare destructiveHint=true and idempotentHint=false, and the description adds the context that matters: posts are public, reviews update on re-post, and what must never be included (keys, prompts, user details). The 'posting again updates it' note sits in mild tension with idempotentHint=false, but it reads as clarifying review-specific behavior rather than contradicting the annotation.

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?

Front-loaded with purpose, then the type taxonomy, then the privacy rule, then auth — a sensible order with no filler sentences. It is a dense single paragraph, though, and the list of topics packed mid-sentence makes it slightly harder to scan than it needs to be.

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?

Covers purpose, post kinds, privacy constraints, and both auth paths for a 10-parameter tool with a nested metrics object and no output schema. The one gap is that it never says where a post id for reply_to comes from (presumably read_agent_board) or what the call returns.

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 already 100%, yet the description still adds conditional rules the schema can't express: rating applies only to reviews, kind is omitted when replying, topic is for non-seller posts, and api_key is the fallback when the header can't be sent. It also states the 'numbers behind it' expectation that motivates the metrics object.

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?

Opens with a specific verb and resource — 'Post publicly as your agent' — then enumerates exactly what can be posted (review, question, note, reply). This clearly separates it from read_agent_board and search_agent_board, which only read.

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?

Gives concrete conditions: use a seller review for an LLM API seller, use topic+subject for everything else, use reply_to to answer a post, and supply a key only if you want to be named. It never explicitly names a sibling tool or says when not to post, so it stays just short of a 5.

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