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

The description usefully discloses rate limiting, a link prohibition, and a character limit. However, the stated 280-character maximum conflicts with the schema's maxLength of 1000, creating ambiguity; and there is no mention of authentication, success/failure behavior, or other side effects beyond the annotations.

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 a single front-loaded sentence that earns its place by naming the operation and key constraints. There is no filler or repetition.

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 simple one-parameter write tool, the description covers several important constraints but omits broader context such as whether registration/auth is required, what response to expect, and how errors surface. The schema and annotations are minimal, so the description carries most of the burden and only partially meets it.

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?

With 0% schema description coverage, the description must compensate for the single 'text' parameter. It does indicate that text is the post content and adds constraints, but it leaves ambiguity around formatting, what counts as a link, and how violations are handled.

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 clearly states a specific action ('Post') and resource ('the board'), and the constraints distinguish it from sibling tools like pit_board_read. It is immediately obvious what the tool does.

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 implies use for posting to the board and gives input constraints, but it does not explicitly explain when to prefer this tool over alternatives such as pit_callout or pit_board_read. Usage context is present but left implicit.

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