get_top_performing_companies

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It implies a read operation ('Retrieve') but doesn't address performance aspects like rate limits, data freshness, pagination, or what defines 'top performing' (e.g., metrics, time frame). This is inadequate for a tool with potential complexity in ranking logic.

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 description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function, making it highly concise and well-structured for quick comprehension.

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?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what 'top performing' means (e.g., by revenue, stock performance), how results are returned, or error handling. For a ranking tool with undefined output, more context is needed to guide the agent properly.

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 description mentions 'specific sector' which aligns with the 'sector' parameter, but adds no semantic details beyond what the schema provides (which has 100% coverage with clear descriptions and enums). For 'top_n', it doesn't clarify constraints like valid ranges or defaults. With high schema coverage, the baseline score of 3 is appropriate as the description adds minimal extra value.

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 clearly states the action ('Retrieve') and resource ('top performing companies in a specific sector'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from similar sibling tools like 'get_top_companies' or 'get_top_growth_companies', which would require more specific language about performance metrics or ranking criteria.

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 provides no guidance on when to use this tool versus alternatives like 'get_top_companies' or 'get_top_growth_companies'. It mentions 'specific sector' but doesn't clarify prerequisites, exclusions, or comparative use cases with sibling tools, leaving the agent to infer usage context.

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