Get Form Layout

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

No annotations provided, so description must disclose key behaviors. The verb 'Get' implies read-only, but the description does not explicitly state it is non-destructive or safe. It mentions preview vs. live retrieval, adding some transparency, but falls short of full disclosure.

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?

Three sentences, front-loaded with purpose, and all content is relevant. No redundancy or wasted 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 (2 params, simple boolean), the description covers purpose, return structure, and use cases. An output schema exists (not shown) but description adequately explains output content. Lacks mention of permissions or idempotency, but sufficient for its scope.

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 coverage is 100%, so baseline is 3. The description adds value by contextualizing the preview parameter with 'Supports both live and pre-live app settings retrieval', which goes beyond the schema's boolean description.

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 retrieves form layout from a kintone app, specifying return details ('rows, subtables, groups, field positioning'). It distinguishes from siblings like kintone-update-form-layout and kintone-add-form-fields by focusing on reading current layout.

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 guides when to use: 'before layout updates' and 'when adding new fields... rearranging existing fields'. It also mentions preview support. However, it lacks explicit when-not or direct comparison to kintone-get-form-fields as an alternative.

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