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

No annotations are provided, so the description alone must convey behavioral information. 'Find' signals a non-mutating lookup, but the description does not disclose match behavior (exact vs. partial, multiple results), how the limit applies, or any external data source/rate-limit concerns.

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 entire description is one compact sentence with no filler. It leads with the action and output objects before the input condition, making it easy to scan and immediately act on.

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 identifier lookup with an output schema present, the description provides the essential query semantics and result objects without needing to restate return values. It is slightly incomplete because it does not mention the limit parameter or when siblings are preferable, but the tool is low-complexity.

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 0%, and the description only adds meaning for the required query parameter by specifying 'name or partial ticker'. The optional limit parameter is left to its schema name/default/min/max, so the description compensates for only half of the parameters.

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 verb ('Find') and concrete resources ('SEC company, ticker, and CIK'), and scopes the input to 'a name or partial ticker'. This clearly distinguishes it from sibling financial-data tools, which focus on snapshots or filings rather than identifier lookup.

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 for resolving a name or partial ticker into SEC identifiers, which provides clear context. However, it never explicitly states when to use this tool instead of a sibling or when another tool would be preferable. Alternatives are not named, so the routing decision is left to inference.

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