freee_get_item

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It states 'Retrieves detailed information' but does not mention that it is a read-only operation, any required permissions, or potential side effects. For a read tool, this is a significant omission.

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 sentence that is front-loaded with the action and resource, then provides a brief elaboration. Every word is necessary and there is no extraneous content.

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?

The tool has no output schema, yet the description only says 'detailed information' without specifying the return structure. For a simple get-by-ID tool, this might be acceptable, but given no annotations, more context about the returned fields (e.g., name, type, pricing) would improve completeness.

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 covers both parameters with descriptions (companyId notes default, itemId described as 'Item ID (品目ID)'). The description adds no additional semantics beyond confirming the item is a product/service item. Schema coverage is 100%, so a baseline 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 'Get a single item (品目) by ID' and specifies it retrieves detailed information for a product/service item. The verb 'Get' directly matches the tool's function, and the resource 'item by ID' is unambiguous. This distinguishes it from sibling tools like freee_get_items, which likely returns a list.

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 such as freee_get_items. There is no mention of prerequisites, typical use cases, or when not to use it. The description lacks context for an AI agent to decide between this and related tools.

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