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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds real behavioral value by disclosing the return shape (canonical identity, aliases, and an availability map with links), which matters because no output schema exists. It omits auth requirements, rate limits, and no-match 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?

A single compact sentence, front-loaded with the entity-locator role and followed by the output inventory. Every clause carries information; nothing is padding.

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 3-param, zero-required lookup with no output schema, the description is nearly sufficient: it explains the resolution behavior and what comes back. The one notable gap is that the schema marks nothing required, and the description only loosely implies that a name, ticker, or CIK must be supplied.

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?

Schema description coverage is 100% and each of q/cik/ticker is documented in the schema itself. The description restates that any of the three identifier forms can be used but adds no format, precedence, or mutual-exclusion detail beyond the schema. Baseline 3 applies.

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 and resource ('resolve a company name/ticker/CIK to its canonical SEC identity + aliases') and names the concrete outputs (aliases and an available_in map with links). This is clearly distinguishable from siblings like company_profile or dossiers, which the description implies happen after the entity is found.

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?

'Use first to find an entity and discover where it has data' gives an explicit ordering cue relative to the rest of the toolset. It does not name a specific alternative or an exclusion, so it falls short of a full when/when-not/routing statement.

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