discover_apps

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

With no annotations, the description carries the full burden. It only says 'Probe,' which suggests a read-only action but does not confirm side effects, authentication needs, or what is returned. This lacks essential behavioral disclosure.

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 sentence and front-loaded, containing no unnecessary words. However, it is too sparse to be genuinely helpful, so while concise, it earns only an average score for structure.

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 low complexity (one parameter), no output schema, and no annotations, the description is incomplete. It does not clarify what 'launch targets' are, what the tool returns, or any typical usage context, leaving significant gaps.

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 0%, so the description must compensate. It hints that deviceId refers to a 'discovered media appliance,' providing minimal context, but does not explain how to obtain the ID or its expected format, offering little value beyond the schema.

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 the specific verb 'Probe' and identifies the resource as 'app launch targets' on a 'discovered media appliance.' This distinguishes it from sibling tools like discover_devices (which finds devices) and search_apps (which searches apps). The term 'launch targets' is somewhat ambiguous but still conveys a clear purpose.

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?

There is no guidance on when to use this tool versus alternatives. The phrase 'discovered media appliance' implies prior discovery, but this is not explicit. No when-not or alternative recommendations are provided.

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