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

Annotations already declare readOnly/not-destructive/closed-world, so the safety profile is covered; the description adds valuable disclosure of the return contents (tables, columns, row counts, content collections) and its role as a prerequisite before read/change operations. It does not mention cost, pagination, or size limits for large sites.

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 tight sentences with the usage trigger front-loaded and the return contents immediately after; no filler or restatement of the title.

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?

Output schema exists, so return values need not be spelled out, and annotations cover safety; the description is nearly complete for a simple read tool. The one gap is the unexplained required site_id, which an agent must infer.

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 0% for the single site_id parameter, so the description would need to compensate but says nothing about it — not where to obtain a site_id (e.g., from list-sites) nor its format. Only the parameter's self-evident name carries any meaning.

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 precisely what is returned: database tables with columns and row counts, plus file-based content collections. This implicitly separates it from get-site-data and the add/update/delete-site-data siblings, but no sibling is named explicitly.

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?

Gives an explicit trigger: 'when the user asks what data their WebTwizz site has, or before reading or changing it', which usefully frames it as a discovery step ahead of the data CRUD tools. No when-not conditions or named alternatives are given.

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