uisp_list_site_data_links

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and resource, without mentioning pagination, ordering, error behavior, or what the returned list contains beyond the name.

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 concise sentence with no filler. The key scoping phrase 'attached to a given site' is front-loaded and immediately clarifies the operation's scope.

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 one-parameter list operation, the description is adequate and the schema covers the parameter well. However, it does not address behavioral expectations or distinguish from the similar global-list sibling, leaving some implicit context.

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 fully documents the only parameter siteId, including its source ('from uisp_list_sites'), so the baseline is 3. The description adds no additional parameter-level context beyond the schema.

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 states a specific verb ('List') and resource ('data links attached to a given site'), which clearly identifies the operation. However, it does not explicitly differentiate from the sibling tool uisp_list_data_links, which likely has a broader scope.

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 implies when to use it: whenever data links belonging to a specific site are needed. It provides no explicit alternative, exclusion, or condition to help choose between this and other list tools, such as uisp_list_data_links.

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