call_microsoft_api

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

The description adds valuable behavioral context beyond annotations. While annotations indicate non-read-only, non-idempotent, and non-destructive operations, the description clarifies this is a 'direct call' tool with 'full control', implying it can perform any HTTP method (including destructive ones like DELETE) and requires careful parameter handling. It doesn't contradict annotations but provides important operational context.

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 functionality. Every word earns its place by clearly stating what the tool does without unnecessary elaboration. It's appropriately sized for a general-purpose tool with extensive parameter documentation elsewhere.

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 complex 18-parameter tool with no output schema, the description provides adequate context about its general-purpose nature. While it doesn't explain return values or detailed error handling, it clearly communicates the tool's scope as a direct API caller. The 100% schema coverage compensates for parameter documentation gaps.

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 18 parameters thoroughly. The description doesn't add significant parameter semantics beyond implying general API calling functionality. It mentions 'full control over HTTP methods and parameters' which aligns with the schema but doesn't provide additional syntax or format details.

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 with specific verbs ('Make direct calls') and resources ('Microsoft Graph or Azure Resource Management API endpoint'), distinguishing it from sibling tools that perform specific operations like managing policies or generating reports. It explicitly mentions 'full control over HTTP methods and parameters', which sets it apart as a general-purpose API caller.

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 implies usage for direct API calls when specific sibling tools aren't suitable, but doesn't explicitly state when to use this tool versus alternatives like execute_graph_batch or execute_graph_search. It provides a general context ('full control') but lacks explicit guidance on use cases or exclusions.

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