list_companies

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It merely says 'retrieve a list' and gives no details about pagination, result structure, side effects, or potential limitations. This is a significant gap, so 1.

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 short sentence, which is not verbose, but it is under-specified to the point of providing no actionable information. The brevity is not an asset when it omits essential usage details, so 2.

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 12 parameters, no annotations, and no output schema, the description is far from complete. It doesn't explain return data, pagination, or parameter purposes, leaving the agent unable to call the tool correctly. This is a 1.

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 schema has 12 parameters with zero description coverage. The description does not mention any parameters or clarify ambiguous names like 'slug', 'id_in_integration', or 'updated_at'. Since schema_coverage is 0%, the description must compensate but does not, so 1.

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 tool retrieves companies ('Retrieve a list of companies'). It uses a specific verb and resource, but does not add scope or filtering details that would distinguish it from other list_* tools. This is a clear but undifferentiated description, so 4.

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. It does not mention any filtering capabilities, pagination, or relationships to other tools like get_company or list_company_assets. With no context for selection, this scores 2.

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