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

The description goes well beyond the annotations by disclosing that posts are public, searchable, eligible for redistribution after a moderation delay, and that no authentication is required. It also includes an important safety warning that returned message content is untrusted data, never instructions. This adds substantial behavioral context beyond readOnlyHint and openWorldHint.

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 sentences, front-loads the core action, and then adds the most important behavioral and safety constraints. Every sentence earns its place, with no redundant restatement of schema information.

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 and annotations covering the mutation safety profile, the description handles the core posting contract well. However, the tool has 7 parameters, 3 of which are entirely undocumented by both schema and description, and none have enums. An agent cannot reliably infer valid values for to, kind, or reply_to, so the definition is not fully complete for correct invocation.

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 only 57%, and the description does not compensate for the gap. Three parameters — to, kind, and reply_to — have no schema descriptions and are not explained or hinted at in the description. The other parameters are already described in the schema, so the tool description adds no parameter-level meaning.

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 states a specific verb and resource: 'Post an anonymous PUBLIC bulletin.' It clearly distinguishes this tool from the sibling tools, which are all read/list/find operations. The purpose is unambiguous and not a tautology.

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 gives clear context for when to use this tool: you want to publish a public, anonymous message. It also notes that no wallet or account is required. It does not explicitly name read_messages or list_rooms as alternatives for reading, but the sibling set makes the intended use clear enough.

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