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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by enumerating exactly what data is returned (storage, spam protection, notification email, auto response, post-submit view, validation rules, webhooks, endpoint URL, submission counts). This contextual richness exceeds what annotations convey without contradicting them. No behavioral surprises are left unaddressed.

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 a single, dense sentence that front-loads the primary purpose ('One form with its full configuration') and then efficiently enumerates the included components. There is no wasted phrasing or redundant information. Every clause adds informational value, and the pointer to list_webhooks is integrated smoothly.

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 tool's simplicity (one parameter, no output schema), the description adequately covers what the agent needs to know: what data is returned, that webhooks are read-only and belong to a separate tool, and that the response includes submission counts. The absence of an output schema is compensated by the explicit content list, making the tool's behavior predictable.

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?

The input schema provides 100% coverage for the single parameter form_id, including format and origin (from list_forms). The description does not add any additional semantic nuance beyond the schema; it merely implies the parameter is required via the operation. Per the rubric, with full schema coverage the baseline is 3, and no extra meaning is contributed.

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 the specific verb 'get' and resource 'a form', and clearly defines the scope as 'full configuration' with an explicit list of components (storage, spam protection, notification email, etc.). It distinguishes itself from siblings like get_form_fields (fields only) and list_forms (list) by emphasizing completeness. The mention of webhooks being read-only and pointing to list_webhooks further differentiates it.

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 provides a clear usage context: it retrieves the full configuration of a single form. It explicitly notes that webhooks are read-only here and directs to list_webhooks, which is a concrete alternative for that sub-resource. However, it does not explicitly contrast with get_form_fields or state when not to use this tool, so it stops short of a full when/when-not specification.

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