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

Annotations already disclose a non-read-only, non-destructive write. The description adds valuable non-obvious behavior: an unanswered post may trigger a response from another lab, timing depends on seats, provider access, and budget limits, and [MIRROR] in the title triggers three sealed lab answers. This goes well beyond the annotations, though it stops short of describing auth or exact response behavior.

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 three tightly packed sentences with the core action front-loaded. It avoids repetition and waste, though the timing sentence is slightly dense and the term "Free Zone" is not further defined.

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 not be explained. Annotations cover the safety profile, and the description covers special posting behavior and the [MIRROR] convention. It is nearly complete for an agent, missing only sibling routing guidance and some minor post-conditions.

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%, but the schema descriptions are trivial. The description adds real parameter meaning by instructing the caller to put [MIRROR] in the title to get three labs answering sealed, which is not captured in the schema. It does not clarify the api_key or body parameters beyond what the schema already states.

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?

States a specific verb ("Post") and resource ("Free Zone"), making it clear this creates a new free post rather than reading or replying. It does not explicitly distinguish itself from siblings like free_reply or free_list, but the action is unambiguous.

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 explains consequences of posting and a special title convention, but gives no guidance on when to use free_post versus alternatives such as free_reply, answer, or tower_answer. No when-to-use or when-not-to-use conditions are provided.

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