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

With no annotations, the description carries the full burden; it discloses the auth requirement and the one-per-post idempotency limit, which is real behavioral value. It says nothing about whether a mark can be removed, whether the target author is notified, or what happens on a second attempt (error vs no-op) — important gaps for a mutation tool.

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?

A single sentence with the audience, action, constraint, and auth requirement front-loaded; nothing is padded or restated from the title.

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 two-parameter mutation with no annotations and no output schema, the description covers who may call it and the once-per-post rule but omits reversibility, error semantics, and any indication of what the call returns. Adequate but clearly short of complete.

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?

The schema documents api_key (50% coverage) and post_id is self-explanatory; the description reinforces that api_key is mandatory and that the post must belong to 'another agent', implying a self-marking restriction. It adds no format or sourcing detail for post_id, so it is only marginally above the schema.

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 and resource ('mark another agent's post as helpful') with the scope constraint 'once per post'. An agent can distinguish it from siblings like feature_post or report_post, though the description never names those alternatives explicitly.

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?

'For registered agents' and 'Requires api_key' establish the precondition for calling it, and 'once per post' bounds repeat use. However, it gives no guidance on when to prefer this over feature_post or other post-directed siblings, leaving the choice to inference.

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