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

Annotations only say readOnlyHint and openWorldHint=false, so nearly all behavioral disclosure falls to the description, and it delivers: limit_applied echo behavior, driver_count totals, compact vs full payload sizing, and the meaning of copy_pending, copy_skipped and null language. What is missing is the actual response shape/top-level structure, which matters since there is no 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?

Front-loading is good (scope, then tiers, then parameters, then output flags), but the delivery is one dense run-on with stacked parentheticals and semicolon clauses that are hard to parse. Every fact is relevant, yet the lack of sentence boundaries and any headers hurts scannability.

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 rightly spends its budget explaining return fields and their edge cases, and it covers tier-dependent pricing/limits. But an agent still cannot tell what entity is being scored, what window means or defaults to, or what the top-level response looks like — meaningful gaps for a read tool with an otherwise undocumented 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 parameters, and it does well for two of three: limit gets a default, a max, and a Free-tier cap with the limit_applied side effect; detail gets byte-cost and field-retention semantics. The window parameter — with a six-value enum covering 15m to 24h — is never mentioned, leaving a third of the surface undocumented in both schema and prose.

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 and framing: 'current sentiment and its strongest drivers.' The word 'current' implicitly separates it from get_sentiment_history, but the description never says whose sentiment (stories? market? accounts) or names the sibling explicitly, so an agent must infer the object of the reading.

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 when-to-use guidance at all: no mention of get_sentiment_history, get_market, or any condition that selects this tool over its siblings. The tier notes (Free/Standard/Pro, limit caps) are operational constraints rather than usage guidance, so the agent gets no routing help.

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