manage_service_principals

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false, which already inform the agent about mutation, non-idempotency, and potential data loss. The description adds minimal behavioral context by mentioning 'permissions, credentials, and enterprise applications,' but doesn't elaborate on side effects, authentication 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 without unnecessary elaboration. It avoids redundancy and wastes no words, though it could be slightly more structured by breaking down the 'including' list 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 (4 parameters, destructive operations, no output schema) and rich annotations, the description is adequate but incomplete. It covers the what but lacks details on behavioral nuances, error handling, or output expectations. With annotations handling safety, it meets minimum viability but leaves gaps for effective agent use.

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%, with clear descriptions for all parameters, including an enum for 'action' that lists specific operations. The description doesn't add any parameter-specific details beyond what the schema provides, such as explaining the 'filter' format or 'spId' sourcing. With high schema coverage, the baseline of 3 is appropriate.

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: managing service principals for application access, with specific mention of permissions, credentials, and enterprise applications. It uses a specific verb ('manage') and resource ('service principals'), distinguishing it from sibling tools like manage_azure_ad_apps or manage_security_groups. However, it doesn't explicitly differentiate from all siblings, keeping it at a 4 rather than a 5.

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 comparisons to sibling tools like manage_azure_ad_apps. Without any usage context, the agent must infer based on the name and parameters alone.

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