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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds the useful scope detail that it lists metadata (tables/columns/row counts, collections) rather than row contents, but discloses no auth needs or limits, and the return format is covered by the output 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?

Two sentences, with the usage trigger front-loaded ahead of the behavioral description. Efficient, though the second sentence packs two distinct return elements and could be slightly tighter.

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 moderate-complexity metadata listing tool with full annotation coverage and an output schema, the description adequately covers when to call it and what it enumerates. The only real gap is site_id semantics, which neither schema nor description addresses.

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% for the single required site_id parameter. The description references "their WebTwizz site" but provides no format, source, or semantics for site_id, so it fails to compensate for the documentation gap.

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 (Lists) and resource (the site's database tables with their columns and row counts, and content collections kept in the site's files). This clearly distinguishes it from the sibling get-site-data, which reads the actual data rather than metadata.

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 what data their WebTwizz site has, or before reading or changing it" gives a clear trigger and a sequencing hint (discovery before get/update/delete). It stops short of naming the alternative siblings explicitly, so it's clear context but not full when/when-not routing.

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