Show Form

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context about returning a JSON object and the API endpoint, but these are beyond annotations. No contradictions.

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 6 sentences, reasonably concise and front-loaded with the purpose. Some redundancy exists ('detailed information' and 'full details'), but it is well-structured and efficient.

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 simple read operation, thorough annotations, and no output schema, the description is adequate. It covers purpose, return type, required parameters, and API context. It could briefly hint at the structure of the returned JSON object, but it's sufficient.

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 baseline is 3. The description mentions required parameters (project_id, id) but does not add additional meaning beyond the schema. The page and per_page parameters are explained in the schema, not in the 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 states 'Return detailed information on the specified Form' with a clear verb and resource. It distinguishes from sibling tools like list_forms_on_a_project by specifying 'fetch the full details of a specific Forms by its identifier.'

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 says 'Use this to fetch the full details of a specific Forms by its identifier,' clearly indicating when to use it. It doesn't explicitly state when not to use it or name alternatives, but the context and sibling names imply that for listing all forms, one would use list_forms_on_a_project.

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