Search Store Applications

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

With no annotations, the description carries full burden. It implies read-only behavior (search/browse) but doesn't explicitly state it's non-destructive. The tab contexts are well-explained, but no mention of prerequisites or side effects.

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?

Four sentences with no redundancy. Front-loads the core action, then breaks down tab contexts, then gives usage intent. Every sentence earns its place.

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?

Covers the main functionality for a list/search tool. Lacks explicit return format, but the limit parameter and absence of output schema make it acceptable. Could mention that results are paginated or sorted, but not critical.

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 reiterates tab_context meanings but adds minimal value beyond the schema's own descriptions. The search_key and limit are clarified but not enhanced.

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?

Clearly states it's for searching/browsing ServiceNow store applications by category, with explicit tab contexts. Distinguishes from siblings like get_app_details or install_store_app by focusing on listing/searching across installed, updates, and available categories.

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?

Describes three tab contexts and their purposes, ending with a direct usage suggestion. Though it doesn't enumerate when not to use it, the advice is clear and actionable.

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