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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds a content preview — 'Each one names its public repository' — but nothing about ordering, completeness, or how the listed templates relate to sandbox templates. Modest added value beyond the annotations.

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?

Three short sentences, front-loaded with the purpose and followed by what the results contain and the next action. Every clause carries information; nothing is redundant.

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, zero parameters, and full annotation coverage, the description needn't describe return values and doesn't try to. The only gap is that it never disambiguates against the adjacent list_site_starters and list_sandbox_templates siblings.

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?

There are zero input parameters, so there is no parameter semantics to explain and the baseline is 4. The mention of templateId is a cross-reference to create_site rather than documentation of this tool's own inputs, which is helpful but not required.

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 and resource ('List the templates') and narrows the scope with 'that a SHIP-hosted site starts from', then enumerates the three kinds (website, blog, docs). It does not explicitly distinguish itself from the similarly named sibling list_site_starters, which an agent could easily confuse it with.

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 a concrete usage path: 'Pass a template id as templateId to create_site', which tells the agent exactly why and when to call this. It stops short of naming alternatives or exclusions (e.g., when list_site_starters is the better choice), so a 4 rather than a 5.

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