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

With no annotations, the description carries the full behavioral burden. It does disclose the returned content surface (configuration, connectors, hosted-page status), which is useful since there is no output schema, but it says nothing about read-only semantics, required credentials, or error behavior for a missing form.

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?

A single economical phrase with no filler and the payload scope stated immediately. It is arguably too terse (an incomplete sentence), but nothing is wasted.

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 one-parameter read tool with no annotations and no output schema, the description is minimally sufficient: it names what the response contains. It omits the safety profile and any usage context, leaving clear gaps.

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% – formId is documented with an example ('frm_abc123') – so the schema does the heavy lifting. The description adds no additional meaning about the identifier format or lookup behavior, making the baseline 3 appropriate.

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 phrase identifies the resource (a form) and the scope of its payload (full configuration, connectors, hosted-page status), but it is a sentence fragment with no verb, so the operation itself is only inferred. It also does nothing to separate this from get_form_snippet or list_forms, which an agent could plausibly reach for instead.

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 statement of when to call this versus the sibling tools (get_form_snippet, list_forms, update_form). The single-form lookup is only implied by the required formId in the schema, not by any prose guidance.

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