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

Annotations already establish the safe read-only profile (readOnlyHint=true, destructiveHint=false), so the description only needs to add context — and it does: it discloses coverage scope ('~300 covered names') and update cadence ('End-of-day'). Those are genuine behavioral traits an agent cannot get from the annotations.

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?

A single dense sentence that front-loads the resource and then lists contents; every clause carries payload. It is jargon-heavy but not padded, and it earns its length for an output-schema-less tool.

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 must describe the return, and it does so thoroughly by enumerating composite rank, all seven sub-scores, and three named ratios. The notable gap is behavior for tickers outside the ~300 covered names, but otherwise an agent has enough to call it correctly.

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 a single parameter at 100% schema coverage, the schema fully documents the ticker input, and the description adds no format or semantics beyond it. Baseline 3 is appropriate when the schema does all the parameter work.

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 names a specific resource (Closelooknet per-ticker signal scores) and enumerates its exact composition: composite rank, seven named sub-scores, and three literature ratios. This is far more than a restated title, though it does not explicitly contrast itself with siblings like get_stock_snapshot or get_df_ranking.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. Usage is only weakly implied by 'per-ticker scoring,' leaving the agent to infer routing among 25 siblings on its own.

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