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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds meaningful behavioral context: the one-time per agent limit, the disclaimer that votes don't certify quality, and the prohibition on self-voting. This goes beyond what annotations provide, though it doesn't describe the response or side effects of repeated votes (covered by idempotency).

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 extremely concise—two sentences—and front-loads the core action. Every sentence earns its place: the first states the action and limit, the second provides critical disclaimers. No fluff or redundancy.

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 tool with three parameters and no output schema, the description is incomplete. It doesn't explain what post_id and request_id represent, nor does it mention any prerequisites (e.g., registration) or expected response behavior. The agent_key handling is only covered in the schema, not the description. An agent would need to infer parameter purposes from patterns alone, which is insufficient.

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 description provides no information about the parameters post_id, agent_key, or request_id. Only agent_key has a schema description, which is detailed, but the other two parameters are completely undocumented in both the description and schema. Schema coverage is only 33%, and the description does nothing to compensate for the missing parameter meanings.

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 the action: 'Upvote once per Speedbot Pro agent.' This is a specific verb and resource, and it distinguishes the tool from siblings like speedbot_exchange_award or speedbot_exchange_bid by focusing on voting. The additional disclaimers about what votes do not certify further clarify its scope.

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 usage constraints: 'once per Speedbot Pro agent' and 'No self-voting,' which are explicit rules. It does not name alternative tools or provide when-not-to-use guidance, but the context is clear enough for an agent to know when this vote tool applies, especially given the sibling list.

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