manage_sharepoint_sites

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 context about the scope of management (creation, configuration, permissions, administration), which helps clarify what 'manage' entails beyond the annotations, but doesn't detail rate limits, authentication needs, or specific behavioral traits like error handling.

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 key information ('Manage SharePoint sites') and lists core functionalities. It avoids redundancy and waste, though it could be slightly more structured by separating actions for clarity.

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?

For a tool with 9 parameters, destructive annotations, and no output schema, the description is adequate but minimal. It covers the high-level purpose and scope, but lacks details on return values, error cases, or operational constraints that would help an agent use it effectively in complex scenarios.

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 the schema fully documents all 9 parameters. The description mentions general aspects like 'creation, configuration, permissions' which loosely map to parameters like action, settings, and owners/members, but adds no specific syntax, format, or usage details beyond what the schema provides, meeting the baseline for high 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 sites including creation, configuration, permissions, and site collection administration.' It specifies the resource (SharePoint sites) and key actions (creation, configuration, permissions, administration), though it doesn't explicitly differentiate from sibling tools like 'manage_sharepoint_lists' or 'manage_sharepoint_governance_policies'.

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, appropriate contexts, or exclusions, leaving the agent to infer usage from the action parameter alone without sibling tool differentiation.

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