sp_share_permission_list

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

The description reinforces the read-only nature indicated by annotations, and adds detail on the scope of permissions included (direct assignments, inherited, sharing links). No contradictions with 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?

The description is concise, front-loaded with the purpose, and every sentence adds value without redundancy.

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 single parameter, existing output schema, and clear scope explanation, the description is complete. It covers usage, return fields, and scope, leaving no ambiguity.

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?

With 0% schema description coverage, the description fully compensates by explaining how to use the url parameter: pass a site URL for site-level permissions or any item URL for item-level permissions.

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 permissions for SharePoint files, folders, or sites, and specifies the returned fields. It explicitly distinguishes from the sibling tool sp_share_link_list, which lists only sharing links.

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 provides explicit guidance on when to use this tool ('before suggesting changes or sharing links') and when to use an alternative (use sp_share_link_list for sharing links only).

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