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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds output-content context ('with expiry dates, registrar, and days remaining') but doesn't disclose additional behavioral traits like pagination behavior or authentication needs, which are partly evident from schema parameters and 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?

The description is a single, front-loaded sentence that conveys the core purpose efficiently with no wasted words. It includes meaningful qualifiers ('tracked') and output specifics without 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 schema parameter coverage, annotations, and an output schema, the description is sufficiently complete. It doesn't need to explain return values (output schema exists) or safety (annotations cover it). The only minor gap is explicit usage guidance, but the tool's simplicity and schema compensate.

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%, with each parameter (limit, cursor, project_id) already described. The tool description adds no parameter-level semantics beyond what the schema provides, so the baseline score of 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 clearly states the verb 'List' with the resource 'tracked domains' and specifies the key output fields ('expiry dates, registrar, and days remaining'). This distinguishes it from sibling list tools like list_monitors or list_projects by clarifying it focuses on domain data.

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?

The description implies usage (you call this when you need domain expiry info), but it does not explicitly state when to use this tool versus alternatives or provide exclusions. The schema parameter 'project_id' references list_projects, which hints at a prerequisite, but the description itself offers no such guidance.

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