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

The description adds operational context beyond annotations (readOnlyHint=true, destructiveHint=false) by detailing permission checks and access blocks. However, it does not describe what the tool returns or any side effects, leaving some behavioral aspects unclear for a tool with no output schema.

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 concise for the amount of guidance it provides, with each sentence adding necessary context. It could be slightly shorter by combining instructions, but it is effectively front-loaded with the purpose.

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?

The description lacks completeness: it omits parameter explanations, return value details, and how to interpret search results. Despite strong usage guidelines, the missing information about inputs and outputs makes it incomplete for a tool with 5 parameters and no output schema.

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?

With 0% schema description coverage and no param explanations in the description, the agent has no guidance on what the five parameters (domain, localized, allPeriods, communityId, registrationPeriodYears) mean or how to use them. The description fails to add any semantic value beyond the schema.

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 'Get pricing' and the resource 'custom domain search result', which aligns with the title. However, it does not explicitly differentiate from sibling tools like 'get_existing_custom_domain_pricing', though the context of a search result implies a distinct scenario.

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 provides explicit usage guidelines: check business permissions, note that FREE businesses cannot use, call check_business_tool_access before proceeding, show grace-period warnings, and never proceed when access is blocked. This clearly tells the agent when and how to use the tool, including prerequisites and exclusions.

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