Get Records

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

With no annotations provided, the description must disclose behavioral traits. It mentions the AND-only filtering constraint, which is a key behavioral detail. However, it does not describe pagination, rate limits, or authentication requirements, which would be beneficial for a comprehensive understanding.

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 extremely concise with two sentences, each serving a distinct purpose: introducing the tool and providing critical usage guidance. It is front-loaded and contains no extraneous words.

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 complexity (6 parameters, nested filtering objects), the description covers the essential aspects: main function, filtering behavior, and a prerequisite. It does not describe the output, but the presence of an output schema compensates for that.

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 schema has 100% description coverage, providing detailed parameter semantics. The description adds value by emphasizing the filtering limitations and the prerequisite of using kintone-get-form-fields for field discovery, aiding parameter usage 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 clearly states it retrieves multiple records from a kintone app with structured filtering, which distinguishes it from sibling tools like kintone-add-records or kintone-get-record-comments. It identifies the specific resource (records in an app) and action (get).

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 explicitly advises using kintone-get-form-fields first to discover available fields, and notes that OR conditions are not supported, guiding the agent on limitations. However, it does not elaborate on when alternatives might be preferred, but given the sibling list, this is sufficient.

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