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

The description goes beyond annotations by explaining the flow: first validate ownership, then return a page for user confirmation via TON Connect. This suggests the tool does not execute the transaction itself but creates the confirmation link. However, it does not disclose potential side effects (e.g., whether a pending state is created) or what happens if validation fails. Since annotations already indicate it is a non-read-only, non-idempotent operation, the added context is valuable but incomplete.

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 sentence (22 words) that conveys the core function without unnecessary detail. It is well-structured and front-loaded with the main purpose, making it easy to scan.

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 string parameter, no output schema), the description is too sparse. It leaves critical questions unanswered: what exactly is 'site', what does the confirmation page contain, and what actions does the user take? The lack of parameter semantics and usage guidelines means the description does not fully equip an agent to invoke the tool 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 input schema defines 'site' as a string with no description, and the tool description does not compensate for this lack. It only implies that the site is the subject of ownership validation, but does not explain what format is expected (e.g., domain name, ID) or provide any examples. With 0% schema coverage, the description should clarify the parameter but does not.

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 tool validates indexed ownership and returns an HTTPS page for confirming a TON DNS site transaction. It is specific about the resource (site) and action (return confirmation page), which helps distinguish it from sibling tools like storage.send_bag_link_tx. However, it does not explicitly name alternatives or delimit scope, so it falls short of full differentiation.

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?

No usage context is provided. The description does not indicate when to use this tool versus alternatives such as directly sending a transaction or using other send_link_tx tools. It lacks prerequisites (e.g., needing to own the site) and does not mention any exclusions or alternative approaches.

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