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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: exactly what each entry contains (code, name, blurb, extra parameters) and where the analyzers actually live (the Supplementary Data menu on quanterlab.com), which tells the agent this is a static local catalog and where the underlying capability runs.

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?

Front-loaded with the purpose sentence, then the return shape, then the site/menu context. Slightly verbose in the second paragraph, but every sentence carries information an agent can use.

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?

With no output schema, the description usefully enumerates the returned fields and clarifies that parameters are per-analyzer rather than for this call. Combined with annotations covering safety, little is missing for a zero-parameter catalog tool; only explicit sibling routing is absent.

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 tool takes no parameters, so the baseline is 4. The description still adds value by explaining that analyzers accept a `ticker` plus additional parameters listed in the returned catalog, which prepares the agent for downstream calls.

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?

States a specific verb (List) and resource (single-stock fundamental analyzers) with the scope 'available in QuanterLab', which distinguishes it from catalog siblings like list_indicators and list_primitives. It stops short of explicitly contrasting itself with those catalog tools, so it is clear but not fully differentiated.

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 the tool is a discovery/catalog call ('this catalog lists what is there'), but gives no explicit when-to-use guidance or pointers to alternatives such as list_indicators or describe_capability. Usage is inferable but not stated.

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