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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only states the basic search/retrieve action. It does not mention pagination, date filtering, response format, rate limits, or any limitations. This is insufficient transparency for a tool with no other structured safety hints.

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 at two sentences and front-loads the core purpose. However, it includes the redundant phrase 'using the FMP Search Crypto News API', which repeats information already implied by the tool name and adds no value. Overall, it is tight but has minor 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?

The tool has five parameters and no output schema, yet the description provides no context on return values, date range usage, pagination, or how the search differs from sibling news tools like getCryptoNews. This leaves the agent with incomplete information for effective use.

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 coverage is 100%, so the baseline is 3, but the description adds a potentially misleading claim that users can enter 'name or symbol', while the schema's required 'symbols' parameter specifically expects comma-separated symbols. This could lead an agent to pass a name like 'Bitcoin' instead of 'BTC'. The description provides no additional clarity on parameters beyond the schema.

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 it searches for cryptocurrency news and retrieves news related to specific coins or tokens by name or symbol. The verb 'Search' and resource 'cryptocurrency news' provide a clear purpose, and the tool distinguishes itself from broader news tools like getGeneralNews, 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?

The description implies usage when needing crypto news for specific coins or tokens, but it provides no explicit guidance on when to use this tool versus siblings like getCryptoNews or searchStockNews. No exclusions or alternatives are mentioned, leaving the decision to the agent.

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