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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful behavior beyond that: the returned fields (clone_url, is_default), the pagination contract (follow next_cursor until has_more is false), and the caveat that site names are dashboard labels, not SEO titles.

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 purpose is front-loaded and each sentence carries operational value (default-site logic, pagination, name semantics). It is dense at five sentences but nothing is filler or 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?

For a read-only, single-project list tool with no output schema, the description covers purpose, return fields, default-selection logic, pagination, and a naming caveat. The only gap is the unmentioned limit parameter and its bounds.

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 0%, so the description must carry parameter meaning. It implies projectId ('within a project') and cursor (via the next_cursor pagination note), but never explains limit, and the cursor mention refers to the response field rather than the input parameter.

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 states a specific verb and resource ('Find the Replo site ... within a project') and frames the tool's intent as inspect/manage/clone, which distinguishes it from sibling list tools like list_projects or list_workspaces. An agent can tell what it does without opening the 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?

It gives explicit decision logic: use the site with is_default=true when the user doesn't name one, and ask for clarification if none is default. It also instructs to page through next_cursor before concluding a site does not exist, covering the when-to-use and when-not-to-conclude cases.

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