Surf News

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context by stating the tool reads articles, fetches full content, and searches sources, which is consistent and adds value without contradicting the annotations.

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 efficiently structured with a usage line, a capability summary, and a command list. It is scannable and each line adds operational detail without unnecessary fluff.

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?

The description covers the commands and their parameters but lacks details like date formats, default values, or response structure. Since there is no output schema, this is a notable gap, though the description provides a solid baseline for a read-only news tool.

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 input schema has 0% coverage for the 'params' object, but the description compensates by listing each command's parameters with types and a few enum values (e.g., sort_by: recency, trending). It also marks id* as required and includes limit/offset for pagination, which is a good compensation.

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 identifies the tool as providing crypto news data, with capabilities to browse articles, read full content, and search by keyword. It distinguishes itself from sibling tools by its focus on news, though it doesn't 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?

It starts with 'Use this when the user needs news data from Surf,' which is an explicit usage signal. It also differentiates commands by listing 'detail' and 'feed' with their respective parameters, providing operational guidance, though no alternative tools are mentioned.

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