list_apps

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

Annotations already declare readOnlyHint=true, so the description does not need to restate that. It adds useful behavioral context by revealing the default filtering behavior ('third-party only by default'), which implies that include_system can override this. This goes beyond the annotations and helps the agent predict behavior.

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 sentence with no fluff, front-loaded with the action and scope. It is appropriately sized for the tool's simplicity and wastes no 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?

For a simple list tool with readOnly annotations, the description covers the core purpose and default behavior. It does not mention the return format or how the optional serial parameter is resolved, but these are partially covered by the schema. Overall it is adequate, though a bit more context on the output would improve it.

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% — serial has a description but include_system does not. The description partially compensates by implying the meaning of include_system through the default filter statement, but it does not explicitly explain the parameter's effect. The agent must infer that setting include_system=true will include system apps.

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 'List' and the resource 'installed packages', and immediately clarifies the default scope with 'third-party only by default'. This distinguishes it from sibling tools like install_app, uninstall_app, launch_app, etc., so an agent can easily tell them apart.

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 no explicit guidance on when to use this tool versus alternatives, nor any conditions or exclusions. It only states what it does. An agent must infer that this is for enumerating installed apps, but no context is given for scenarios like checking before launching or filtering.

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