kintone_get_record

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

No annotations are provided, so the description carries the full burden. It states the basic operation but does not disclose behavioral traits such as authentication requirements, rate limits, error handling (e.g., missing record), or that it performs a read-only operation. The warning about using list_apps is helpful but not about the tool's own behavior.

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 with no fluff. The core purpose is in the first sentence, and the prerequisite hint is in the second. It is appropriately sized and 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?

For a simple tool with two required parameters and no output schema or annotations, the description provides the basic function and a prerequisite hint. However, it lacks details on error handling, return format, and any limitations. Adequate but with gaps.

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?

Input schema has 100% description coverage for both parameters, already explaining them. The description adds marginal value by reiterating the hint for app_id. Schema provides sufficient semantics, so baseline 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 tool's purpose: 'Get a single record from a Kintone app by record ID.' It uses a specific verb ('Get') and resource ('record'), and distinguishes itself from siblings like 'kintone_get_records' (multiple records) and 'kintone_create_record' (create).

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 a prerequisite hint: 'Use kintone_list_apps first to get available app IDs.' This guides the user on a necessary step before using the tool. However, it does not explicitly mention when not to use it or alternatives, though siblings make it implicit.

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