Get Records

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

With no annotations provided, the description must disclose key behaviors. It states that filters are AND-combined and OR is unsupported, which is a critical limitation. However, it does not mention authentication requirements, rate limits, or what happens on errors (e.g., invalid app ID). The behavioral disclosure is incomplete.

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: two sentences front-load the purpose and immediately provide a crucial usage hint (use kintone-get-form-fields first). Every word adds value; no redundancy.

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?

Despite the tool's complexity (6 parameters with nested objects, multiple filter types, an output schema), the description is minimal. It does not explain pagination behavior (offset/limit), maximum record limits, or error cases. The missing details leave the agent under-informed for effective use.

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%, so the baseline is 3. The description adds no significant meaning beyond what the schema already provides for each parameter. It emphasizes 'structured filtering' but does not clarify 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 the action ('Get multiple records') and resource ('kintone app') with 'structured filtering'. It implies the tool is for reading records, distinguishing it from mutation tools like kintone-add-records or kintone-update-records. However, it does not explicitly contrast with other retrieval tools like kintone-get-app or kintone-get-form-fields, though the names themselves differentiate.

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 advises using kintone-get-form-fields first to discover fields, and notes that OR conditions are not supported. This provides helpful context but does not specify when NOT to use this tool (e.g., for OR logic there is no alternative mentioned). It lacks guidance on pagination or handling large result sets.

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