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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's "Read-only" is largely redundant, but it adds cost information ($0.00/free) that no annotation conveys and discloses the full payload surface. It stops short of noting whether output is static or account-specific, which would matter for caching.

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?

Single front-loaded sentence with the verb first and the enumerated contents after, so an agent can stop reading early. The trailing "Read-only and free ($0.00)" partly repeats the readOnly annotation, and the four-name parenthetical is dense, but no sentence is wasted.

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 carries the burden of describing return values, and it does so by naming the four archetypes and the per-archetype fields returned. Missing only shape/format details (e.g., whether demo URLs are strings or lists), which is minor for a zero-parameter static catalog 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. No parameter meaning is lost.

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?

Opens with a specific verb+resource ("List the 4 executive outbound micro-page archetypes") and then enumerates all four by name plus the exact payload (recommended columns, synonym mappings, demo URLs, prompt guidance). An agent can distinguish this from siblings like list_lists, list_sheets, or list_prompts without opening any 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?

Usage is only implied: the mention of "upstream run_ai enrichment prompt guidance" hints this is a discovery step before running run_ai or creating a list, but the description never states when to call this instead of list_lists/list_sheets, nor any preconditions. Adequate context, no explicit routing guidance.

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