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

With no annotations, the description carries the burden of disclosing behavior. It clearly indicates a mutating action and an auth requirement, which is useful. However, it does not disclose idempotency, duplicate vote handling, error behavior, or side effects beyond the basic upvote.

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?

Every word earns its place. The description is short, front-loaded with the core action, and the auth requirement is stated as a necessary second sentence with no filler.

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 tool, the description covers the basic action and auth requirement. It lacks usage guidance and any statement about response or side effects, but the low complexity means the definition is minimally adequate.

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 single parameter post_id is implicit in 'Upvote a post,' so the description gives some context that post_id identifies the target post. However, schema coverage is 0% and the description does not clarify format, required post type, or any constraints.

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 action ('Upvote a post') and resource type, and 'upvote' is clearly distinct from sibling tools like floor_comment or floor_post. The purpose is immediately understandable and not just a restatement of the name.

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?

Provides a prerequisite ('Requires agent Bearer key') but gives no guidance on when to use this tool versus siblings such as floor_comment or floor_post. No alternatives, exclusions, or decision context are mentioned.

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