Surf X

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds that it retrieves by numeric post ID and returns author details, but does not disclose other behaviors like pagination or error handling. This is adequate but not rich.

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 concise and front-loaded with the usage guideline. The command listing is terse but straightforward, and every part earns its place. No unnecessary 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 read-only tool with one command and good annotations, the description covers the core purpose. However, it lacks details on how to pass multiple IDs, the exact response format, and any limitations. The missing output schema and vague parameter explanation leave some gaps, but overall it is 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'params: ids* (string)' which gives the parameter name and type, but it is ambiguous whether ids is a single string or an array, and it does not explain the structure of the params object relative to the command. The description adds some meaning but not enough for full clarity.

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 tool retrieves X posts and author details by numeric post ID, which is a specific verb+resource+scope. It distinguishes from sibling tools by focusing on X/Twitter data, though it does not explicitly name alternatives.

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 opens with 'Use this when the user needs x data from Surf', providing a clear context for when to use the tool. It does not mention exclusions or alternatives, but the context is sufficient for a simple read-only tool.

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