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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds context about the data categories returned but does not disclose pagination behavior, rate limits, or how the limit parameter affects results. It is consistent with annotations, so no contradiction, but it provides limited additional behavioral insight beyond the listed data.

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 a single, front-loaded sentence with no redundant words. It immediately states the purpose and enumerates the outputs efficiently, making it easy to parse and act upon.

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 tool with robust annotations, the description provides enough to understand what data is returned, but it omits how the limit parameter applies across multiple data types and does not mention exchange disambiguation. Since there is no output schema, a brief note on return structure would improve completeness, but the description is adequate for basic use.

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 67% (symbol and exchange have descriptions; limit lacks a description but has constraints). Since coverage is moderate, the description should compensate by explaining parameter usage, but it does not. The description mentions the data categories but not how limit or exchange interact with the query, leaving agents to infer from schema defaults and bounds.

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 states a specific verb 'Get' and a clear resource 'analyst research' while enumerating the exact data categories (price targets, recommendation trends, rating changes, earnings estimates, revenue estimates). This level of specificity distinguishes it from sibling tools like company.financials or company.statements, making the purpose unambiguous.

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 implies usage when analyst research data is needed, but it does not explicitly mention alternatives or conditions when this tool should not be used. It lacks guidance on when to prefer this over similar tools like company.financials or market.quotes, though the specificity of the data types gives some implicit context.

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