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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context beyond those fields: that the content is static documentation and touches no workspace data, meaning results don't vary by workspace or state. It doesn't discuss size or whether the full guide is large, which is a minor gap.

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 compact sentences front-load the identity of the resource, then the contents, then the scoping caveat. The parenthetical example list is dense but every clause maps to a distinct section of the guide, so nothing reads as 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?

An output schema exists, so return structure need not be explained, and the description covers the remaining burden: what the guide contains, that it is static, and what the single optional part parameter selects. For a one-parameter, read-only documentation tool this is fully sufficient to invoke correctly.

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% and the enum already documents all, rules, config_schema, and examples, so the schema carries the baseline. The description still adds meaning by expanding what the parts contain, notably that examples include a lead form, a scored quiz, and a score-gated booking page, which helps an agent predict whether fetching a part answers its question.

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 names a specific resource (the dForms form config reference) and enumerates its contents: rules, workspace selection, step types, logic, scoring, JSON Schema, and worked examples. It also anchors itself against siblings by naming create_form and update_form, whose rules it documents, so an agent can distinguish it from the mutation tools 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?

The framing 'the rules create_form and update_form check' gives a clear implicit condition for use (consult before or when building/updating a form) and 'Static documentation; it reads no workspace data' rules out expecting live data. It stops short of explicit when-not-to-use language or naming a competing reference tool, so it's strong context rather than full routing guidance.

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