freee_set_company_token

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

The description lacks details about side effects, such as whether setting a token overwrites previous tokens, if it persists across sessions, or if it requires specific permissions. With no annotations to fall back on, the description should disclose these behaviors but does not.

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, clear sentence that efficiently conveys the tool's purpose. It is not verbose, but it could benefit from slightly more detail without becoming wordy. Still, it is appropriately concise.

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 that the tool modifies authentication state and has 4 required parameters, the description is too minimal. It does not explain what happens after setting the token (e.g., subsequent API calls use it), any validation, or dependencies. More context is expected for a tool with this level of complexity and no output schema.

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%, with each parameter already described (companyId, accessToken, refreshToken, expiresIn). The tool description does not add any additional meaning beyond the schema, 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 the action (set) and what it operates on (access token for a specific company). It distinguishes from sibling tools like freee_get_access_token (which retrieves tokens) and freee_clear_auth (which clears authentication), making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., freee_get_access_token, freee_auth_status). There is no indication of prerequisites, such as having already obtained a token via OAuth, or scenarios where manual setting is appropriate.

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