Get Form (Dalux Field)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety and idempotency. The description adds 'with all its answered fields' but doesn't provide additional behavioral context such as rate limits, authentication prerequisites, or error handling. With annotations present, the description's extra value is moderate.

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?

Description is a single precise sentence with no extraneous words. Essential information is front-loaded, achieving high efficiency.

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 low complexity (simple fetch, few parameters) and absence of output schema, the description adequately conveys the core functionality. However, the lack of output schema means agents must infer return format; a slightly richer description could 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?

Input schema has 2 required parameters with 50% description coverage (projectId described, formId not). The tool description does not add any parameter-specific meaning. For a schema with partial coverage, baseline 3 applies as the description neither compensates nor significantly enhances understanding.

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?

Description uses a specific verb 'Fetch' and clearly identifies the resource 'one form with all its answered fields'. It distinguishes from siblings like dalux_list_forms and dalux_get_task, making the tool's purpose immediately clear.

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 implies usage when needing a single form's details but provides no explicit guidance on when to use this versus alternatives like dalux_list_forms (for listing) or differences in field availability. No exclusion or when-not-to-use context is given.

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