infomaniak_list_short_urls

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds the account-scoped nature of the listing, which is useful context beyond the annotations. No contradictions or additional behavioral details are necessary for this read-only operation.

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 that immediately conveys the tool's purpose. It is front-loaded with the action 'List' and includes the essential scope ('your account' and the service). No filler or unnecessary details.

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?

The tool is simple with only two optional pagination parameters, and the output schema covers return values. Annotations cover safety and idempotency. The description provides enough scope information, and there are no missing behavioral or usage details that would hinder correct invocation.

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 has two parameters (page, per_page) with defaults and constraints, but the description provides no additional meaning or explanation of pagination. Schema description coverage is 0%, so the description should compensate, but it doesn't mention that the tool is paginated or how the parameters behave.

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 clear resource: short URLs on Infomaniak's url-shortener service. It also scopes to 'your account,' which differentiates it from sibling tools like infomaniak_create_short_url and infomaniak_short_urls_quota.

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 clearly implies this is the read/list operation for short URLs, with no ambiguity. It doesn't explicitly state when not to use it or mention alternatives, but given the simple nature of the tool and clear sibling context, the intended usage is evident.

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