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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), but the description adds genuinely new behavior: per-variable output shape (name, set state, managing connector) and a redaction rule that public NEXT_PUBLIC_ values are shown while secrets never are. Permission requirements or pagination behavior are not mentioned.

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: trigger first, return shape second, value-visibility caveat last. Nothing is redundant and the most decision-relevant information is front-loaded.

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 correctly compensates by describing returned fields and the secret-redaction rule. It leaves open whether variables unset on the site are included and whether the user needs any permission, but an agent has enough to invoke it 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?

The single required parameter site_id is undocumented in both the schema (0% coverage) and the description; 'their WebTwizz site' only weakly implies that site_id selects the scope. With one parameter and no schema text, a modest gap remains but is not severe.

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 (lists environment variables/settings keys for a site) and even enumerates the returned fields, so an agent can tell it apart from data-oriented siblings like list-site-data and get-site. It doesn't explicitly name a sibling, so it stops short of the top mark.

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?

"Use this when the user asks which settings or keys their WebTwizz site has" gives a clear triggering condition that maps directly onto a user intent. No when-not guidance or named alternative (e.g. vs get-site or list-connectors) is offered.

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