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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety. It adds valuable behavioral context by listing exactly what is excluded (customer identifiers, internal ids, message bodies, etc.), which is crucial for privacy expectations and beyond what the schema or annotations provide.

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?

A single, tightly worded sentence that front-loads the core action and scope, then lists exclusions without redundancy. Every word earns its place, making it easy for an agent to quickly grasp the tool's behavior.

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 an output schema present, the return format is covered elsewhere. The description adequately explains the scope and exclusions for a read-only overview tool with one optional parameter. It does not mention what 'recent' means in terms of time window, but the exclusions and bounded nature are sufficient for correct invocation.

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 100%, meaning the schema already fully documents the optional 'websiteId' parameter. The description adds the phrase 'bounded organization-scoped' which reinforces that the parameter filters within the organization's websites, but it does not introduce substantive new meaning beyond the schema's own description.

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?

The description starts with a specific verb 'Render' and clearly identifies the resource as a 'bounded organization-scoped snapshot of Supovia websites and recent conversations'. It distinguishes itself from sibling list tools by framing the output as a composite snapshot rather than a list, making its purpose unambiguous.

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?

The description implies this is for getting a high-level overview, but it does not explicitly state when to use it versus the sibling list_websites, list_conversations, or show_customer_inbox tools. There is no mention of conditions under which one alternative is preferable, though the word 'snapshot' hints at a summary view.

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