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 genuinely non-obvious behavior: that email_notifications.effective_recipients resolves the real delivery target, including the site-owner default when nothing is configured — a computed-value disclosure an agent could not get from the schema.

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?

Three tight sentences: return contents first, then the resolved-recipients caveat, then the prerequisite. The trailing 'Take the slug from list_forms' mildly duplicates the schema note but earns its place as an invocation hint.

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 enumerates the returned shape, and all parameters are schema-documented. It omits error behavior for an unknown slug and any permission requirements, which are the only remaining gaps for an otherwise simple read tool.

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%, so all four parameters are already documented in the schema, giving a baseline of 3. The description only restates the slug provenance and says nothing about variation_id (which design variation is read) or user_goal, so it adds no meaning beyond structured data.

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?

Enumerates exactly what the tool returns (fields, submit button text, submission settings), which tells an agent this is a single-form read rather than a listing. It implicitly distinguishes itself from list_forms by saying the slug comes from there, but never names update_form_settings as the write counterpart or uses an explicit verb like 'get' in the description body.

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?

'Take the slug from list_forms' gives a concrete prerequisite and routing hint for the required form_slug argument. There is no explicit when-not guidance or pointer to the mutation sibling, so the agent still has to infer that this is the read path.

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