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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value by disclosing the depth and scope of what is returned (post-submit config, notification/confirmation emails, captcha, deal creation), which the annotations cannot convey.

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 front-loaded sentence with the operation first and the enumerated payload after the colon; no filler sentences and nothing repeated from the annotations.

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?

With no output schema, the description usefully compensates by naming the returned configuration areas, and annotations cover the safety profile. It stops short of noting whether field identifiers needed for a follow-up update_form are included, a minor gap.

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% with a single documented parameter ('Form id or slug'), so the schema already carries the semantics. The description echoes 'by id or slug' without adding format, casing, or error behavior beyond the schema — baseline 3.

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 ('Read one Smart Form's full configuration by id or slug') and then enumerates the exact contents returned (fields, copy, post-submit behavior, emails, captcha, deal creation, is_active). An agent can separate it from list_forms (plural listing) and update_form (mutation) without opening a 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?

Usage is implied by 'Read one ... by id or slug', which signals the single-record lookup case, but there is no explicit when-to-use versus list_forms, nor any stated prerequisite (e.g. needing a form id from list_forms first). Adequate but with a clear gap.

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