Search Microsoft first-party apps

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

No annotations provided, so description must handle transparency. It discloses that the result is a summary without AppRoles, but does not mention idempotency, auth requirements, or potential mutation. For a search tool, this is adequate but not thorough.

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 two concise sentences with no fluff. It front-loads the core purpose and provides a key distinction, making every sentence valuable.

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?

The description covers the return format (summary without roles), default limit (25), and the relationship with get_microsoft_app. For a simple search tool with no output schema, this is fairly complete, though it lacks pagination details.

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%, with both parameters having descriptions in the schema. The description adds no extra meaning beyond what the schema provides, so baseline score 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 action is to search Microsoft first-party applications by display name or AppId, and it distinguishes itself from get_microsoft_app by noting it returns a summary without AppRoles array.

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 explicitly tells the agent to use get_microsoft_app for an app's roles, providing a clear alternative. However, it does not address when to use other sibling tools like search_app_roles or search_graph_permissions.

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