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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the core safety profile is known. The description adds useful context beyond annotations: 'No account access, no order placement or fund transfers' and 'Not investment advice', which prevents misuse. It also states 'Read-only public research data', reinforcing and extending the annotation. No contradictions; the description complements annotations well.

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 front-loads the core function and outputs, then provides routing guidance, then disclaimers. It is moderately concise with no wasted sentences, though it duplicates the routing guidance from the schema (which is acceptable but slightly redundant). Structure is logical and an agent can grasp the purpose quickly.

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 simple read-only query with two optional parameters and an output schema, the description is complete from an agent's perspective: it states what it does, what it returns, when to use alternatives, and safety constraints. It even disclaims investment advice. Nothing an agent needs to invoke it correctly is missing.

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 both parameters (coin and time_range) already have thorough descriptions in the input schema, including examples (BTC or BTC,ETH) and default values. The description itself adds little new parameter semantics—it repeats the routing statement already present in the coin parameter description. Baseline 3 is appropriate because the schema does the heavy lifting and the description does not conflict or add meaningful additional detail.

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 aggregates per-coin social sentiment for a time range and lists the specific outputs (overall sentiment, positive/negative split, mention count, sample tweets). It also distinguishes itself from sibling tools by explicitly routing X/Twitter post search to search_x and multi-platform thread search to search_ugc, so an agent can immediately tell them apart without opening 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?

The description provides explicit when-to-use guidance: it names sibling tools (search_x, search_ugc) and the specific conditions (tweet-level evidence vs. multi-platform threads). It also states that it is read-only public research data and disclaims investment advice, which clarifies appropriate contexts. No ambiguity remains about when to select this tool over alternatives.

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