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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context that it produces code and does not install anything or mutate a program, reinforcing the non-destructive nature beyond the annotation defaults.

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, front-loaded with the core action, then the constraint, then the sibling routing. No filler, and each sentence adds a distinct decision-relevant fact.

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 read-only code-generation tool with an output schema, the description covers purpose, scope limits, and alternatives adequately. The remaining gap is that the nested participant/auth parameter details are left entirely to a schema that has no per-field descriptions.

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 0%, so the description must compensate. It signals the two meaningful inputs ('Choose `element`' and 'optionally include participant authentication attributes'), which maps to the enum and the withAuthAttributes/participant params, but it does not document the enum options, the required email inside the nested participant object, or the default of withAuthAttributes.

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 ('Generate one embeddable element's HTML as Markdown') and explicitly distinguishes itself from two named siblings. An agent can identify the tool's role without opening the 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?

It names the alternatives and the conditions that select them ('growsurf_client_snippets for a broader browser integration or growsurf_grsf_config_snippet for page-level participant auto authentication') and clarifies the negative case ('Does not install the element or change a program').

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