Search app roles across Microsoft apps

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

With no annotations, the description carries full burden. It discloses the search scope (keyword in Value, DisplayName, Description) and output elements (AppId, AppDisplayName). It does not mention auth, rate limits, or edge cases, but for a search tool this is adequate and transparent.

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, front-loaded with action and scope. Every word adds value. No fluff.

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 2 params and no output schema, the description explains output content (AppId, AppDisplayName) which is helpful. It covers essential context for a search tool but lacks details on error handling, pagination beyond limit, or no-result scenarios.

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%, so baseline is 3. The description's example for query ('EventGrid', 'Policy.Read') adds marginal value beyond the schema description. The limit parameter is not elaborated in the description, so no additional meaning beyond 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 it searches app roles by keyword across Microsoft first-party apps. It specifies the fields searched (Value, DisplayName, Description) and notes the output includes owning app's AppId and AppDisplayName. This distinguishes it from sibling tools like search_graph_application_permissions or search_microsoft_apps.

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 when to use: to find which app exposes a given role. However, it does not explicitly state when not to use this tool or compare it with alternatives like search_graph_application_permissions. It provides clear context but lacks exclusions.

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