search_apps

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It reveals that the tool searches only 'allowed' sources, does not download, and persists candidates locally—key traits beyond a simple search. It does not, however, mention error handling, return behavior, or side effects beyond persistence.

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?

A single, front-loaded sentence contains no fluff. Every word contributes meaning, and it efficiently conveys both the primary action and the persistence side effect.

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?

In the absence of an output schema, the description should explain what the tool returns (e.g., candidates, success status, or a list). It mentions persisting candidates locally, which implies a side effect but not the return payload. It also does not clarify what 'candidates' are or how they might be used with sibling tools like 'get_analysis' or 'download_app'.

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?

The description does not mention any of the three parameters, and schema coverage is 0%. While parameter names and defaults are present in the schema, the description adds no extra clarity about 'query', 'limit', or 'sources', leaving the agent to infer meaning (especially for valid 'sources' values).

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 uses a specific verb ('Search') and resource ('allowed app sources') and clarifies the non-downloading nature, effectively distinguishing it from sibling 'download_app'. The addition of 'persist candidates locally' further specifies behavior beyond the tool name.

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 implicitly contrasts with downloading by stating 'without downloading', giving the agent a clear when-not-to-use signal. It also notes a side effect (persistence), but does not explicitly name alternative tools or exhaustive when-to-use conditions.

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