Find Umeng apps by keyword

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

No annotations are provided, so the description bears full responsibility. It describes the search operation but omits behavioral traits such as pagination behavior (via maxPages), result format, error handling for no matches, or read-only nature. The description lacks detail beyond the basic action.

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 sentences: the first captures the action, the second provides usage context. It is appropriately sized, front-loaded, and free of unnecessary words.

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 large set of sibling tools and no output schema, the description is incomplete. It does not mention pagination details, result structure, or how this tool relates to similar search or list tools. Agents lack guidance on interpreting results or handling the maxPages parameter.

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 50%; the keyword parameter is described similarly in both schema and description, adding no new value. The maxPages parameter lacks any description in either schema or tool description, leaving its purpose and behavior unexplained.

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 verb 'search' and the resource 'applications', specifying searchable fields (name, platform, appkey) and raw JSON. It distinguishes from sibling tools like umeng_get_all_apps which lack keyword filtering.

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 provides a usage context ('us when the agent only knows part of the app name') but does not explicitly mention alternatives like umeng_get_all_apps for full list scenarios, nor does it specify when not to use this tool.

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