manage_sharepoint_sites

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

Annotations indicate this is a non-readOnly, non-idempotent, destructive tool. The description adds some behavioral context by mentioning 'permissions' and 'site collection administration', which hints at security and administrative scope. However, it doesn't elaborate on the destructive nature (e.g., what 'delete' action entails), rate limits, or authentication requirements beyond what annotations provide.

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 wastes no words, 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?

Given the tool's complexity (9 parameters, destructive hint, no output schema), the description is adequate but incomplete. It covers the high-level scope but lacks details on output format, error handling, or specific behavioral traits like the implications of destructive actions. Annotations help, but more context would improve completeness.

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 100% schema description coverage, the schema already documents all 9 parameters thoroughly. The description adds minimal value by implying parameters like 'permissions' (mapping to owners/members) and 'configuration' (mapping to settings), but doesn't provide additional syntax, format, or usage details beyond the schema.

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 enumerates key actions (creation, configuration, permissions, administration), though it doesn't explicitly distinguish 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, context for choosing specific actions, or how it differs from related sibling tools like 'manage_sharepoint_lists' or 'manage_sharepoint_governance_policies'. Usage is implied through the action parameter but not explicitly stated.

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