list_share_links

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

With no annotations provided, the description must disclose behaviors like pagination, return structure, and scope. It only states 'List share links,' providing zero behavioral information about what the operation does beyond the literal words.

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, terse sentence that simply restates the tool name. While short, it under-specifies and fails to provide useful information, meaning the sentence does not earn its place.

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?

This is a list operation with no output schema or annotations, yet the description does not explain what a share link is, how pagination works, or how it differs from similar tools like 'list_shares'. The minimal description leaves crucial gaps for an agent.

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 provides descriptions for all three parameters ('q', 'page', 'per_page'), achieving 100% schema description coverage. The description adds no extra parameter semantics beyond what the schema already provides.

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 'List share links' is a direct restatement of the tool name, making it a tautology. It does not clarify what constitutes a share link or distinguish this from the sibling tool 'list_shares'.

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?

There is no guidance on when to use this tool instead of other listing tools like 'list_shares' or 'list_access_requests'. No context is provided about use cases or alternatives.

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