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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The 'AI-scored' wording signals derived rather than raw data, which is mild added context, but nothing is said about scoring latency, coverage gaps, or empty-result behavior for a company with no announcements.

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?

Two tight sentences with the core purpose front-loaded and the return detail following. No filler, though the enumerated return fields are somewhat list-like and redundant given an output schema exists.

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?

Output schema exists so return values need not be explained, yet the description spends its second sentence doing exactly that. Combined with full annotation coverage and 100% schema coverage, the only real omission is routing guidance against sibling sentiment tools.

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 all six parameters (ticker, from, to, limit, hedging, sentiment filters) are already documented in the schema. The description adds no filter syntax or default behavior beyond that, so the baseline 3 applies.

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 verb and resource: AI-scored sentiment analysis of NZX announcements for a company, plus the scope (-1 to +1 scores, confidence, hedging). Clear and non-tautological. However, it never differentiates itself from close siblings such as get_news_sentiment, get_capital_raise_sentiment, or get_disclosure_language, leaving the agent to guess which sentiment surface applies.

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, no when-not-to-use, no prerequisites, and no named alternative among the many sibling sentiment/disclosure tools. The description only says what the tool returns, not the situation that selects it.

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