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

With no annotations provided, the description carries the full transparency burden. It only says 'comprehensive view' and 'bulk data' without disclosing response format, pagination, rate limits, or any potential side effects, which is insufficient for a bulk data endpoint.

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 two sentences and front-loaded with the tool's purpose. The first sentence is somewhat redundant with the name, but the second provides concrete content. It is concise and avoids unnecessary details.

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?

Given there is no output schema and this is a bulk data tool, the description should clarify the return structure or note any limitations. It merely says 'retrieve bulk data' without explaining the output format, size, or any other contextual expectations, leaving the agent under-informed.

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?

The schema has zero parameters, so the baseline is 4. The description correctly implies no parameters are needed by stating 'across all symbols', but it adds no parameter-specific detail beyond that which is unnecessary given the empty schema.

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 retrieves bulk data for analyst upgrades, downgrades, and consensus recommendations across all symbols. It uses specific verbs and a defined resource, though it does not explicitly distinguish it from sibling tools like getStockRatingsBulk or getPriceTargetConsensus.

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 no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or scenarios where another tool would be more appropriate, leaving the agent without decision-making context.

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