execute_delta_query

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe, repeatable operation. The description adds value by specifying the tool's purpose for 'tracking incremental changes' and 'efficient synchronization,' which gives context beyond annotations, but does not detail behavioral aspects like rate limits, authentication needs, or 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, well-structured sentence that efficiently conveys the tool's purpose, method, and benefit without any redundant or unnecessary information. It is front-loaded with key information and uses precise language.

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 moderate complexity, rich annotations, and full schema coverage, the description is largely complete for its purpose. However, the absence of an output schema means the description could benefit from mentioning return values or pagination behavior, leaving a minor gap in contextual information.

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 both parameters ('resource' and 'deltaToken'). The description mentions 'delta queries' which aligns with the deltaToken parameter, adding some semantic context, but does not provide additional details beyond what the schema already covers, such as examples or constraints.

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 specific action ('track incremental changes'), the resource ('Microsoft Graph resources'), and the method ('using delta queries'), with explicit mention of the benefit ('for efficient synchronization'). It distinguishes this tool from siblings by focusing on delta query functionality rather than batch operations, searches, or management tasks.

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 context for 'efficient synchronization' scenarios, suggesting when to use this tool for tracking changes over time. However, it does not explicitly state when not to use it or name specific alternatives among the sibling tools, such as 'execute_graph_search' for non-incremental queries.

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