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

With no annotations, the description must disclose behavioral traits itself. It says 'retrieve,' which suggests a read-only operation, but provides no details about rate limits, prerequisites, or the nature of the output. This is insufficient given the lack of annotation support.

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 concise. The first sentence states the purpose clearly; the second adds context about the value of the scores but is somewhat generic. It earns its place without excessive verbosity.

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 no annotations, the description should compensate by explaining what data is returned or any operational constraints. It only says 'financial scores and metrics' without listing specific metrics or return format, leaving significant ambiguity.

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 input schema has no properties, so there are no parameters to document. Per the rubric, a baseline of 4 applies for zero-parameter tools. The description adds no parameter info, but none is needed.

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,' identifying both the verb and resource. It distinguishes itself from singular tools like getFinancialScores via the 'Bulk' mention and 'multiple symbols,' though it could be more explicit about the exact metrics included.

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 use when needing scores for multiple symbols quickly, but does not explicitly state when to use this over alternatives (e.g., getFinancialScores for a single symbol) or provide exclusion criteria. The guidance is inferred rather than stated.

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