Trending developments

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered. The description adds real behavior: the time windows per kind, that kind=slot caps at 10 stories per slot over 7 days, that `trending` labels encode slot membership and rank, and that each item carries source/sentiment counts and a newest statement.

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?

Front-loaded with the one-line purpose and the when-to-use trigger, then structured by parameter. Dense but each sentence carries a distinct fact; the only mild redundancy is restating the kind live/slot windows already in the schema.

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?

No output schema exists, yet the description characterizes the return payload (source count, sentiment counts, newest statement, trending slot/rank labels) and the slot-range limit caveat, which is what an agent needs to call and interpret this correctly.

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 baseline is 3, but the description adds constraints not obvious from the schema: symbol takes one code only, and limit is taken from the top of the API ranking with `total` in the result revealing the true count. kind semantics are reinforced rather than merely repeated.

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 (the developments most outlets are reporting) and its live/slot scopes, and names the sibling find_topics as the alternative for a different time window. An agent can distinguish it from siblings without opening any schema.

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?

Explicit routing instructions: use for 'what is moving right now' (kind=live, last 2 hours), and if you want the whole day rather than 2 hours, use find_topics with sort=velocity. It even tells the agent to raise limit when kind=slot's top-of-slot isn't enough.

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