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 covered. The description adds the behavioral detail that the tool returns a list of all websites with specific fields, but does not mention pagination behavior or any other runtime traits. This is acceptable but not richly transparent.

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?

The description is a single sentence that is front-loaded with the trigger condition and includes the key return fields. There is no wasted text, and it is easy for an agent to parse quickly.

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 read-only list tool with full parameter documentation, annotations, and an output schema, the description covers purpose and scope well. The only minor gap is that saying 'all' websites could imply a single response, while limit/offset parameters suggest pagination may be needed. Overall, the definition is nearly complete.

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%, so the parameters limit, offset, and context are already fully documented in the schema. The description mentions output fields rather than parameter details, adding no parameter semantics beyond the schema. Baseline 3 is appropriate.

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 clearly states the operation: list all websites, and enumerates the returned fields (name, slug, preview URL, production URL). It distinguishes itself from siblings like get_app and find_app by emphasizing 'all' websites. This is a specific, non-tautological purpose.

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 explicitly says when to use this tool: when the user wants to see all their websites. It does not name alternatives or exclusions, but the scope is clear enough that an agent is unlikely to confuse it with get_app or find_app. A 4 is appropriate because the usage context is clear, though alternatives are not discussed.

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