fiken_list_companies

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

No annotations are provided, so the description carries full burden. It mentions listing for the authenticated user and slugs, but does not disclose pagination behavior, rate limits, or error conditions. The description adds minimal behavioral insight beyond the schema.

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 two sentences, directly stating the purpose and a usage hint. No extraneous information, all sentences are necessary and efficient.

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 list tool with pagination, the description is sufficient. It explains the main output (slugs) and relevance to other tools. No output schema exists, but the tool's return is implied. Slight improvement could mention pagination limits.

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 100% (page and pageSize have descriptions). The description does not add extra meaning beyond the schema parameters, so a baseline score of 3 is appropriate.

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 'List all companies the authenticated user has access to.' This is a specific verb+resource combination that distinguishes it from sibling tools which focus on individual entities or other list operations.

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 includes 'Use the returned slugs with other tools,' which provides clear context on how the output is used. While it does not explicitly state when not to use it, the entry-point nature is evident. Among siblings, fiken_get_company is the alternative for getting a specific company.

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