freee identity

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is clear. The description adds the 'authenticated' requirement and 'API backend' availability, which are not in the annotations. However, it does not disclose return format, pagination, or error behavior. Given the strong annotation coverage, the added context is adequate but not rich.

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 short sentences with no redundant language. It front-loads the action ('Read') and immediately specifies the resource. Every word serves a purpose, and it conveys the essential information efficiently.

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 low complexity (no parameters, no output schema) and the strong annotations, the description is nearly complete. It states the input (none), the operation (read), and the resource (identities). It could optionally detail what 'identities' includes, but the tool name and sibling context make it sufficiently clear for an agent to select and invoke correctly.

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 tool has zero parameters, so the schema fully covers the input space. With no parameters, the description correctly omits parameter details, and no additional semantics are needed. The baseline for 0 parameters is 4, and the description does not introduce any confusion.

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 states a clear verb 'Read' and a specific resource: 'the authenticated freee user and company identities'. This distinguishes it from sibling tools like freee_clock_status or freee_approval_list, which focus on different domains. The phrase 'Available on the API backend' adds deployment context without obscuring the primary purpose.

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 implies usage context through 'authenticated' and 'API backend', suggesting it is for retrieving current user/company info on the backend. However, it does not explicitly mention when not to use this tool or name alternatives like freee_auth_status, which might also relate to identity. The guidance is implied but not fully explicit.

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