list_supported_tlds

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

With no annotations, the description carries full burden. It explains that the data is derived from a cached pricing table and that force_refresh=True bypasses cache. This discloses key behavioral traits, though no mention of rate limits or other side effects.

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 three short, efficient sentences. The primary purpose is front-loaded, and each sentence adds necessary information without superfluous 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 the tool's simplicity (one boolean param, no output schema), the description covers the key aspects: what it returns, sorting, and cache behavior. It could mention output format, but it's not critical.

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 of 0% means the property descriptions are empty. The description adds meaning by explaining that force_refresh=True bypasses the cache, which is essential for the agent to understand the parameter's effect.

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 it lists all TLDs Porkbun supports for registration, sorted alphabetically. The verb is implied (list), the resource is TLDs, and the scope is clear. No sibling tool overlaps significantly.

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 mentions the relationship to get_pricing (same cache) and explains the force_refresh parameter to bypass cache. While not explicitly stating when to use this tool vs alternatives, the context is clear enough for an agent.

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