Check blocked domain

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the check may include the registrable parent domain and names the blocked-domains list, but it does not describe the return value shape, read-only nature, or failure behavior.

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 two compact sentences with the core check stated first and usage guidance second. There is no wasted text.

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 one-parameter check with full schema coverage, the description gives enough context to select and call the tool. The main remaining gap is that it does not explicitly state the return value, though 'Check whether' implies a Boolean-style result.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics by saying the check applies to the domain or its registrable parent, which goes beyond the schema's hostname example.

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 uses a specific verb and resource: it checks whether a domain is on the StellarExpert blocked-domains list. It also clarifies the important scope that the registrable parent may be checked. It does not explicitly name the sibling list_blocked_domains, but the singular check purpose is still clear.

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 gives a clear usage condition: use it before linking or recommending a Stellar-related URL. It does not state when not to use it or point to alternatives such as listing all blocked domains, so it falls short of the highest level.

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