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

No annotations are provided, so the description carries the full burden. It claims users can find ETFs 'by their name or ticker,' but the input schema has no parameters, which is misleading. It also fails to disclose output format, whether it returns a full list, or any 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?

The description is two sentences and front-loads the purpose, but the second sentence is partly redundant ('simplifies identifying specific ETFs by their name or ticker') with the first. Still compact and readable.

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?

The tool is simple (0 params, no output schema), but the description is incomplete: it does not explain what the output represents (full list vs. filtered results) or clarify the 'by name or ticker' claim. This leaves the agent uncertain about invocation behavior.

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?

With 0 parameters, the baseline is 4, but the description actively misleads by implying search filters ('by their name or ticker') that do not exist in the schema. This contradicts the schema and does not add meaningful parameter semantics.

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 finds ticker symbols and company names for ETFs, providing a specific verb and resource. It does not explicitly distinguish itself from sibling tools like getETFQuotes or searchSymbol, so it loses a point.

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 for identifying ETFs by name or ticker, but does not mention when to use this tool over alternatives such as searchSymbol or getETFQuotes. No exclusions or specific context is given, leaving it at an implied level.

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