Retrieves additional required fields for country-code top-level domains (e.g., .tr) before adding a domain to the cart.
Domain additional fields for ccTLDs (.tr etc.) before agent_cart_add.
| Name | Required | Description | Default |
|---|---|---|---|
| tld | No | TLD without dot; omit for all |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It does not disclose what the tool does (read vs. create), what data it returns, whether it modifies state, or any side effects. It only hints at a dependency from agent_cart_add, leaving behavioral ambiguity.
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 short sentence, concise and front-loaded with the resource name. It earns its place by being brief, though it sacrifices detail for brevity.
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 the tool's context (part of a domain registration flow with many siblings), the description is incomplete. It does not explain what 'additional fields' means, what the output is, or how it integrates with agent_cart_add. It lacks information an agent needs to use it correctly.
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 schema has 100% coverage for the single 'tld' parameter with a description. The description adds no additional meaning beyond the schema, except implying tld is used for filtering ccTLDs. Since coverage is high, baseline 3 is appropriate, but no extra value is provided.
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 'Domain additional fields for ccTLDs (.tr etc.) before agent_cart_add.' indicates a resource (domain additional fields) and a vague verb ('for'), but it is unclear whether this tool retrieves, validates, or defines these fields. It does not clearly distinguish from siblings like search_domain or list_tlds; it only mentions a positional relationship to agent_cart_add.
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?
It states 'before agent_cart_add' implying a sequencing, but does not explain when to use this vs. alternatives like list_tlds or search_domain. It does not mention any conditions, exclusions, or alternatives; the context is minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.