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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful items beyond that — the auth requirement (X-API-Key or Bearer token) and the return shape ('decision-ready rows, not a raw feed'). It still says nothing about rate limits, result caps, or freshness/lag of 'live' clusters.

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 core verb and ranking criteria, then use cases, then the auth caveat as a trailing parenthetical. Two sentences with no filler; the auth note is slightly tacked-on but earns its place as a prerequisite.

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?

With no output schema, the description does enough: it tells the agent the result is pre-ranked rows with phase/velocity/source-count rather than a feed, and flags the credential requirement before the call. The remaining gap is that the two optional parameters are left entirely to the schema.

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 carry the burden — and it mentions neither parameter. 'vertical' has four enum values (crypto, finance, tech, turkish) whose selection semantics are unexplained, and 'emerging_only' is never addressed. An agent can guess from the names, but nothing is confirmed.

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 concrete verb+resource with its ranking criteria ('Ranked live narrative clusters by phase, velocity and distinct-source count'), which is far more specific than the bare title 'Narratives'. It doesn't explicitly name muhabbit_narrative_history as the contrasting tool, so differentiation relies on the agent inferring 'live' vs. 'history' from names.

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?

Gives concrete use cases ('themes, rotations, or "what's the story in crypto right now?"') that map cleanly to an agent's intent matching. It stops short of stating when NOT to use it or naming the sibling (narrative_history) that handles historical lookups.

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