sp_share_link_list

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description reinforces read-only behavior ('Does not create or revoke') and adds scope context (only sharing-link permissions). No contradictions. Additional information about what the tool does not do adds transparency beyond annotations.

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?

Three concise sentences. First sentence states purpose and fields. Second sentence clarifies read-only nature. Third sentence provides usage alternatives. No redundant words; every sentence adds value.

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 (1 parameter, list operation, read-only) and the presence of an output schema (not shown but implied), the description fully covers purpose, behavior, parameter meaning, and usage guidance. No gaps for effective 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?

Schema coverage is 0% (parameter description empty). The description explains the 'url' parameter as the SharePoint file or folder URL, adding critical meaning. While it doesn't specify format or validation rules, it provides enough context for agent to understand the parameter's purpose.

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 lists existing sharing links on a SharePoint file or folder, enumerates the fields of each entry, and differentiates from siblings by naming specific alternatives (sp_share_link_create, sp_share_link_revoke, sp_share_permission_list).

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?

Provides explicit when-to-use (list sharing links) and when-not-to-use (for creation, revocation, or broader permission listing) with direct references to sibling tools. Also clarifies scope limitation to sharing links only.

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