get-me-domain

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

Description covers safe read-only operation (annotations confirm readOnlyHint=true) and specifies what data is retrieved. OpenWorldHint is noted but not contradicted. Description adds context about data fields beyond 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?

Single, front-loaded sentence that efficiently communicates purpose and included fields with no wasted words.

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?

Given single parameter with full schema coverage, no output schema, and simple read operation, description is sufficiently complete. Sibling tools cover related listing and DNS operations, so context is adequate.

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?

The input schema already provides detailed description and pattern for domain-id (100% coverage). Description reiterates the format and mentions it's from Muumuu Domain, adding slight clarity but schema already suffices.

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?

Description clearly states the verb 'Fetch full details' and specific resource 'a single owned domain by its Muumuu domain ID', listing included fields (contract period, auto-renewal, nameserver config) distinguishes it from siblings like list-me-domains.

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 this tool is for getting details of a single domain, contrasting with list-me-domains for listing all. However, no explicit guidance on when to use alternatives or when not to use this tool is given.

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