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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds the completeness claim ('every deal this server can verify'), which tells the agent this is the exhaustive enumeration path. It says nothing about result size or pagination, a mild gap for a full-list operation, but the presence of an output schema offsets that.

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?

Two short sentences, zero waste, with the scope and returned fields front-loaded and the sibling redirect placed last.

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 params, full annotation coverage and an output schema that documents return values, the description covers what an agent needs to select and call it. The only missing nuance is expected result volume for an unbounded enumeration.

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 zero parameters, so there is nothing to document; the baseline for a no-param tool applies. The description correctly implies no filtering arguments exist and that filtering requires find_deals.

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 ('List every deal') plus the scope ('this server can verify') and names the returned fields (CIKs, aliases, filing periods). An agent can distinguish it from find_deals without opening either schema.

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?

Explicitly routes focused lookups to find_deals, which is the nearest sibling and the main confusion risk. It lacks an explicit 'when not to use' beyond that, but the enumerate-vs-lookup split is clear.

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