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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds only that results are scoped to an 'entitled' saved website map, which is a small but real access/side constraint; it says nothing about what 'readiness' indicates, pagination behavior, or result shape.

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?

Brevity here is under-specification rather than economy: a single noun phrase with no verb and no front-loaded action. Nothing is wasted, but nothing useful is delivered either.

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 7-parameter read tool with no output schema and low schema coverage, the description should explain what is returned and how the filters interact. It does neither, so an agent cannot reliably invoke it without guessing.

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?

Seven parameters with only 29% schema description coverage means the description must carry meaning for url, area, days, limit, offset, and direction. It explains none of them; 'pages and readiness' gives no hint about how area, direction, or days alter the result, leaving most inputs undocumented anywhere.

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 fragment 'Pages and readiness in the entitled saved website map' never states a verb and never says what 'readiness' means, so the agent cannot tell whether this returns page records, a status report, or both. It also fails to distinguish itself from close siblings like read_site, read_page_keywords, and read_page_connections, which each name a concrete resource.

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?

There is no statement of when to call this versus read_site or read_page_insights, and no prerequisites beyond the implied 'entitled saved website map'. The agent must infer selection criteria entirely from the name and the sibling list.

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