freee_get_companies

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

With no annotations provided, the description carries the full burden. It states the tool retrieves data and implies a read-only operation, but does not disclose authentication requirements, potential errors, or rate limits. However, the behavior is simple and adequately described for a list retrieval, earning a mid-range score.

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 concise with three sentences: first states purpose, second explains usage importance, third provides caching guidance. Every sentence adds valuable information with no redundancy, and the most critical information is front-loaded.

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 tool's simplicity (no parameters, no output schema), the description fully covers what the tool does, why it's useful, and how to handle results (cache). It provides sufficient context for an AI agent to know that this is a prerequisite for many other freee tools.

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 input schema has zero parameters, so schema description coverage is effectively 100%. The description adds no parameter details, which is appropriate since none exist. The baseline for zero parameters is 4, as the description cannot add value beyond the schema.

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 explicitly states 'Get list of accessible companies' and 'Retrieves all companies linked to your freee account in one call', which clearly identifies the action and resource. It distinguishes itself from the sibling 'freee_get_company' by indicating it returns a list rather than a single company.

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 clear usage context: it's the 'essential first step to get company IDs for subsequent API calls' and suggests caching due to infrequent changes. While it does not explicitly list when not to use or name alternatives, the context strongly implies it is for initial setup, not for retrieving specific company details.

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