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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context by disclosing what each row contains (indexing status, pages indexed/found, last indexed time, last error), which matters because no output schema exists. It omits pagination/result-size behavior, keeping it from a 5.

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 front-loaded sentence that names the action first and appends the returned fields. Every clause carries information; there is no filler or redundancy.

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 simple read-only list tool with full annotation coverage and a 100% documented schema, the description is nearly complete, and it compensates for the absent output schema by listing the returned fields. It is only slightly short on operational details such as ordering, pagination, or how often indexing status updates.

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 both parameters (collection_id and in_workspace) are fully documented in the schema. The description only echoes the collection scoping implicitly and adds nothing about parameter format or side effects, so the baseline 3 applies.

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 ('List the websites of a knowledge collection') and enumerates the fields it returns, which implicitly separates it from siblings like collections_list_files and collections_add_website. It does not name any sibling explicitly, so it stops short of full differentiation, but the purpose is 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?

Usage is only implied: an agent can infer this is the way to inspect a collection's websites, versus collections_add_website or collections_refresh_website. There is no statement of when to prefer this call, no prerequisite (e.g. the collection must exist or that indexing is asynchronous), and no exclusions.

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