crypto_articles

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

The description discloses the time window (last 24 hours) and sorting order (newest to oldest), which are helpful behavioral traits. However, it does not mention pagination, response format, or any caveats, and with no annotations the burden on the description is higher.

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 very concise at two sentences, with the main purpose front-loaded. Every sentence provides relevant information without unnecessary detail.

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?

There is no output schema, so the description should explain the structure of the returned articles. It only says 'list of Articles' without specifying fields or count. It also lacks pagination behavior and differentiation from similar tools, making it incomplete for a new agent.

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 100%, so every parameter has a description. The tool description adds no additional parameter semantics, which is acceptable given the schema already documents the parameters.

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 returns a list of Articles from the last 24 hours, sorted newest to oldest. It specifies the verb and resource, but does not differentiate it from sibling tools like 'latest_news' or 'crypto_articles_search_by_keywords'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions or the existence of search-related siblings, leaving the agent uncertain about selection.

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