apps

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

With no annotations, the description must convey behavioral traits. It only repeats the tool name without disclosing details such as whether the list includes all apps or only user-installed, the return format, or side effects. The 'appsFilter' parameter is in the schema but not mentioned in the description.

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 a single short sentence, which is concise. However, it does not earn its place because it provides minimal value beyond the tool name. It is not verbose, but it could be more informative without adding length.

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 tool has 18 parameters and no output schema, the description is severely inadequate. It does not explain what kind of app list is returned, how to filter, or what the output looks like. The high parameter count demands a more comprehensive description.

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 description coverage is 94%, so the schema already documents most parameters. The description adds no additional parameter context. According to rubric, baseline is 3 for high coverage, and the description does not improve or worsen that.

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 'List installed apps' clearly states the action and resource. However, it does not differentiate from sibling tools like 'install', 'appstate', or 'snapshot' which could also relate to apps. The verb 'list' is specific, but the description could be more precise about what is listed.

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?

No guidance is provided on when to use this tool versus alternatives like 'install' or 'appstate'. There is no mention of prerequisites, context, or scenarios where listing apps is appropriate. The description lacks any usage direction.

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