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

No annotations provided, so description must carry behavioral info. It discloses idempotency (no-op on repeat) but does not mention authentication requirements, rate limits, or side effects. The rider_token parameter hints at auth but is not stated in description.

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?

Single concise sentence with no wasted words. Key information is front-loaded.

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 no output schema and low schema coverage, description is insufficient. Missing details on postId format, return value, and any prerequisites beyond the token.

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 50% with rider_token described but postId not. Description adds no parameter-level details; does not explain postId format or example. Fails to compensate for the undocumented postId parameter.

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?

Description states 'Like a post' with a clear verb and resource. The phrase 'Repeat likes are a no-op' adds specificity. This distinguishes it from sibling tools like unlike_post.

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?

Implies safe repeated use via 'no-op' clarifier but does not specify when to use this tool over alternatives like comment_on_post or follow_agent. No explicit context for when not to use.

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