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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds value by stating there is no account access, no order placement or fund transfers, and that it is not investment advice. This goes beyond what annotations provide, though it doesn't detail response format—which is covered by the output schema.

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—two sentences—and front-loads the core purpose, then adds routing and warnings. No wasted words; every sentence earns its place, making it efficient for an agent to parse.

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?

For a tool with 13 parameters and an output schema, the description covers purpose, sibling differentiation, and behavioral constraints. It doesn't need to explain parameters because the schema does that, and the output schema covers return values. It is complete for the description's role.

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% and parameter descriptions are very detailed (e.g., query explains similarity vs heat mode, coin explains when it is sent). The description itself doesn't add parameter-level semantics but relies on the schema, so baseline 3 is appropriate.

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 the platform news index for headlines, news items, and briefing-style result lists. It uses a specific verb and resource, and explicitly differentiates from web_search and get_latest_events, so an agent can tell them apart without inspecting schemas.

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?

Explicitly names alternatives and the conditions that route to them: open-web research with synthesized answers goes to web_search, and event catalog with event_id goes to get_latest_events. Also clarifies it's read-only research with no account access or orders, setting clear context for when to invoke.

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