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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds behavioral context by listing the exact fields returned, which goes beyond annotations, but it does not cover edge cases like missing tickers or data latency. This is a meaningful but not exhaustive addition.

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 concise sentence that front-loads the action and enumerates key fields without unnecessary words. Every phrase earns its place.

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 lookup tool with an output schema and comprehensive annotations, the description covers purpose, parameter semantics, and expected output fields. It lacks alternative usage guidance, but that is addressed in the usage guidelines dimension. Overall, it provides sufficient information for correct invocation.

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 one parameter ('ticker') with no description (0% coverage). The description compensates by stating 'single ticker', clarifying that exactly one symbol is expected, and the schema example 'AAPL' provides format context. However, it does not elaborate on valid formats or constraints, leaving some ambiguity.

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 uses a specific verb ('Fetch') and resource ('full Massive reference details for a single ticker'), and enumerates the fields returned (company name, description, SIC code, etc.). This clearly distinguishes it from sibling tools like 'tickers' (plural) and 'entity_profile' by emphasizing 'single ticker'.

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 clear context: use this for a single ticker's reference details. However, it does not explicitly name when to prefer this over alternatives like 'tickers' or 'entity_profile', nor does it state exclusions, so it lacks explicit alternative guidance.

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