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

With no annotations, the description carries the full burden. It does disclose genuinely useful behavior – that ranking is by change in share of all papers over a defined 3-vs-3-month window – which is the key non-obvious trait. But it says nothing about ordering, result volume, rate limits, or permissions, so significant ground is uncovered.

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?

A single dense sentence with the metric and comparison window front-loaded and no filler. Nothing could be trimmed without losing information.

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 return values need not be explained, and the metric definition is the hardest part to convey – the description does that well. However, with zero parameter documentation and no annotations, an agent still lacks enough to choose direction values or a sensible limit.

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 for both parameters and does not. The 'rising/fading' intent in the title loosely maps to the direction enum, but the enum values are never named, and the limit parameter (1-25) is not mentioned at all.

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?

States a specific resource (AI research ideas) and the exact metric/scope it is ranked by: change in share of all papers, last 3 months vs the prior 3. An agent can tell what it returns. It does not, however, differentiate itself from conceptually adjacent siblings like find_breakouts or rising_companies.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. The direction enum and the title hint that this is for spotting rising/fading topics, but that is inference rather than guidance.

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