Show a form

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. "Reads community data" largely duplicates readOnlyHint and adds no new behavioral detail such as which community/account context is resolved or what is returned.

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?

Two very short sentences, front-loaded, with no wasted words. However, the brevity reflects under-specification rather than efficient information density; it is minimal but thin.

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?

The tool is simple (2 params, no output schema) and annotations carry the safety profile, but the description omits any differentiation from the cluster of form-related siblings (list_forms, update_form, delete_form, duplicate_form, get_form_submissions). An agent would have to guess this is the single-form fetch rather than a list or submission endpoint.

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%: form_id and account are both documented in the schema, including the useful note that account selects credentials rather than a remote community ID. The description adds nothing about parameters, so the baseline of 3 applies.

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?

"Show a form" merely restates the tool name and title (get_form / "Show a form") without a distinct verb-resource relationship an agent can act on. "Reads community data" hints at scope but does not say what a "form" is or how this differs from siblings like list_forms or get_form_submissions. It is close to a tautology.

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?

There is no guidance on when to use this tool versus alternatives such as list_forms, get_form_submissions, update_form, or duplicate_form, all of which are present in the sibling list. No prerequisites, no exclusions, no context.

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