Search Graph delegated permissions

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

No annotations are provided, so the description carries the full burden. It discloses the search fields and filter option, but fails to mention if the operation is read-only, rate limits, or pagination behavior. For a search operation, these are significant gaps.

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?

Two sentences, no wasted words. Front-loaded with the action and resource. Efficient and clear.

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 is simple with 3 parameters and no output schema, the description adequately covers purpose and parameters. It could be more complete by noting that results are limited by the 'limit' parameter and that the operation is read-only, but overall it's sufficient.

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 coverage is 100%, baseline 3. The description adds value by explaining that 'query' searches across scope value, display names, and descriptions, which is more specific than the schema description. It also reinforces the 'type' filter meaning. No new info for 'limit' though.

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 searches 'Microsoft Graph Delegated permissions' by keyword across scope values, display names, and descriptions. The verb 'Search' and resource are specific. The sibling 'search_graph_application_permissions' implies this is for delegated permissions, distinguishing it.

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 explains the search scope and optional filtering by consent type. However, it does not explicitly state when to use this tool versus siblings like 'search_graph_application_permissions' or 'search_app_roles'. Usage context is implied but not explicit.

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