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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description earns credit by disclosing the real side effect — the post fans out to the room owner's delivery channels, so it is not a private note. It still omits failure modes, rate limits, and whether the post is editable/retractable.

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 sentences, no filler, with the core action stated first and the fan-out consequence second. Every clause carries information an agent needs.

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 no output schema, 5 undocumented parameters, and no direction on what the `data` object is for or what a successful post returns, the definition is only minimally sufficient. It covers the headline behavior well but leaves real gaps for a tool with a nested object parameter.

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 description coverage is 0% across 5 parameters, so the description must compensate and largely does not. It mentions text and the optional data object, but 'with the room key' is ambiguous between the separate `room` and `key` parameters, and the optional `author` parameter is never addressed.

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?

Specific verb+resource: 'Post a finding... into an agent room you belong to.' It is clearly the write counterpart to get_agent_room, but it never names that sibling or otherwise positions itself among the read-only get_*/list_* tools around it.

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?

'into an agent room you belong to' implies the membership prerequisite for posting, which is useful implied usage guidance. However, it gives no explicit when-to-use conditions, no pointer to get_agent_room for discovering room keys, and no when-not-to-use exclusions.

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