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

With no annotations, the description carries the full behavioral burden, and it only discloses that results are ranked by magnitude. It says nothing about what a 'measure' is, the direction of ranking, whether this is a live scan or cached data, or any rate/permission constraints.

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 efficient sentence with the resource and ranking behavior front-loaded and no wasted words. The compactness is appropriate, though part of the brevity comes at the cost of clarity rather than being purely economical.

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 one-parameter tool with no annotations and no output schema, the description is too thin: the core concept ('measures', 'how much') is never defined and no return shape is hinted at. An agent could not confidently predict what comes back.

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 single parameter (limit, max 25) is not mentioned in the description at all. The max-25 cap and default behavior are left entirely for the agent to infer, so the description does not compensate for the coverage gap.

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?

'Companies breaking out on two or more measures, ranked by how much' states a resource (companies) and a rough action, but 'measures' and 'how much' are undefined jargon. It does not distinguish itself from the sibling find_breakouts, whose name suggests near-identical behavior, leaving the agent unable to tell them apart.

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 when-to-use statement, no prerequisites, and no mention of alternatives. The presence of a sibling literally named find_breakouts makes this omission material, since the two tools are not differentiated anywhere in the text.

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