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

The description adds the important scoping detail that results are limited to collections controlled by the authenticated wallet, complementing the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint). It does not contradict annotations and provides meaningful behavioral context beyond the structured hints.

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, front-loaded sentence that states the action, resource, and scope with zero wasted words. It is perfectly appropriate in length.

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 list endpoint with optional pagination parameters and no output schema, the description covers the essential scope and action. It could have mentioned pagination behavior, but the schema plus annotations provide adequate context for this low-complexity tool.

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 description coverage is 0%, and the description does not mention pagination or the semantics of 'limit' and 'cursor'. Although the parameter names are conventional, the description fails to clarify that these are pagination controls, leaving the agent to infer their use from the schema alone.

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 ('List') and a specific resource ('TON Subdomain collections controlled by the authenticated wallet'), clearly distinguishing it from siblings like subdomains.get_collection (single item) and subdomains.list_items (items within collections).

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 clear context: it lists collections owned by the authenticated wallet, implying a read-only, scoped operation. It does not explicitly mention alternatives or exclusions, but the scope and sibling names make the intended usage unambiguous.

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