getFinancialScoresBulk

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering safety. The description adds that it returns scores for multiple symbols, but lacks details on data freshness, rate limits, or pagination behavior.

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 sentences efficiently convey the core purpose and benefit. No unnecessary words; front-loaded with the action and resource.

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 no output schema and zero parameters, the description should explain how symbols are determined and what the output looks like. It leaves ambiguity about symbol selection and result format, making it incomplete despite annotations.

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?

No parameters exist in schema (100% coverage), so baseline is 4. However, the description mentions 'multiple symbols' without explaining how they are specified, implying a missing parameter or assumption about scope, which reduces clarity.

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 'financial scores and metrics for multiple symbols', using specific verb 'retrieve' and resource 'scores', differentiating from sibling getFinancialScores by explicitly mentioning 'Bulk' and 'multiple symbols'.

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?

No guidance on when to use this tool versus alternatives like getFinancialScores or other bulk endpoints. No mention of prerequisites, symbol selection, or when not to use.

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