Get a form

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

No annotations are provided, so the description carries the full burden and does well: it declares 'Read-only' and discloses the tenant-scoping behavior (unknown id yields not-found rather than another tenant's form), which is genuine behavioral context. It stops short of auth requirements or explicit return shape, but the scoping and safety profile are covered.

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 short sentences, front-loaded with the core action, then the safety/scoping trait, then the routing hints. Every sentence carries distinct information; no filler.

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?

For a single-parameter read tool with no output schema, the description says what is returned ('full field and settings definition'), how ids are obtained, what happens on a bad id, and what sibling covers submissions. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3, but the description adds real meaning about formId: it is resolved against the tenant's form list and an unknown value produces a not-found error rather than a cross-tenant lookup. That is more than the schema's 'UUID of the form' conveys.

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?

States a specific verb and resource ('Get one form') and quantifies scope ('its full field and settings definition'), which separates it from the list/collection siblings. An agent can distinguish it from list_forms, create_form, and delete_form without opening any schema.

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?

Explicitly routes the agent: 'Use list_forms to discover ids; use list_submissions for responses.' Both prerequisites (need an id first) and the alternative for a different resource are named, leaving nothing to inference.

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