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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds mild behavioral color by implying the result is a ranked, truncated ('top') list of domains rather than a complete one, but says nothing about authentication needs or how 'top' is ranked.

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 short, front-loaded sentence with zero filler. It is arguably too terse given the missing routing and scope detail, but there is no wasted language to penalize.

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 two-parameter read tool with full schema coverage and annotations that cover safety, the description is adequate but leaves two real gaps: no distinction from list_source_urls and no hint of what 'top' means or how results are ordered. With no output schema, ordering/ranking semantics would have been the highest-value addition.

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 limit (default 20, max 50) and workspaceId (with pointer to list_workspaces) are fully documented in the schema. The description adds no parameter detail beyond this, so 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?

States a specific verb+resource ('List top source domains') and adds scope via 'cited by AI models', which is more informative than the name alone. However, it gives no differentiation from the sibling list_source_urls, which sounds closely related, so an agent cannot route between them from this text.

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?

Pure statement of function with no when-to-use guidance, no prerequisites, and no mention of when list_source_urls would be the better choice. The only usage-relevant fact (workspaceId is required) lives in the schema, not the description.

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