manage_sharepoint_lists

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false, covering safety and idempotency. The description adds minimal behavioral context beyond this, such as the broad scope of management (schema, items, views, permissions), but doesn't detail side effects, auth needs, or rate limits. No contradiction with annotations exists.

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, efficient sentence that front-loads the core purpose. It avoids redundancy and waste, though it could be slightly more structured (e.g., separating scope items with commas). Overall, it's appropriately concise for the tool's complexity.

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 complexity (8 parameters, destructive operations, no output schema) and rich annotations, the description is adequate but incomplete. It covers the general purpose but lacks details on return values, error handling, or operational constraints, leaving gaps for an agent to infer behavior from the schema and annotations alone.

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 description coverage is 100%, so parameters are well-documented in the schema. The description implies parameters relate to managing lists/libraries but doesn't add specific meaning beyond what the schema provides, such as explaining how 'action' interacts with other parameters. Baseline 3 is appropriate given high schema coverage.

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's purpose: 'Manage SharePoint lists and libraries including schema definition, items, views, and permissions.' It specifies the resource (SharePoint lists/libraries) and scope (schema, items, views, permissions), though it doesn't explicitly distinguish from sibling tools like 'manage_sharepoint_sites' or 'manage_sharepoint_governance_policies' beyond the general 'lists and libraries' focus.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, nor does it reference sibling tools for comparison. Users must infer usage from the action parameter and schema alone.

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