List websites

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile is covered. The description adds return fields (id, name, domain, createdAt) and emphasizes the tool as a dependency. However, it does not disclose pagination behavior, rate limits, or authentication requirements beyond the 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 no waste. First sentence states purpose and scope; second sentence provides imperative call-to-action and lists key return fields. Information is front-loaded and efficient.

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 fields are not strictly required. The description still lists key fields. It explains the tool's role as a prerequisite. For a list tool with pagination parameters, it lacks mention of pagination behavior, but the schema covers that. Overall, adequate for the complexity.

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 100%, so the baseline is 3. The description mentions 'including team sites' which relates to the includeTeams parameter, but this is already described in the schema. No additional parameter explanations beyond schema descriptions.

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 action ('List') and resource ('websites'), and specifies scope ('every website you can access, including team sites'). It distinguishes this tool from siblings as the primary listing tool for websites, unique among many sibling tools.

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?

Explicitly states 'CALL THIS FIRST' and explains why ('every other tool needs a website ID from here'). This provides clear when-to-use guidance and establishes prerequisite relationships with other tools.

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