xbox_installed_apps

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

With no annotations, the description carries the full behavioral burden. It implies a read-only fetch but discloses nothing about required prerequisites (a sibling xbox_power_on exists, suggesting the console may need to be awake), latency, result size, or failure modes when the console is off or unpaired.

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 front-loaded sentence with zero filler; it says exactly what the tool retrieves and from where, and nothing more.

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 zero-parameter read tool the sentence is arguably enough, but the absence of annotations and of an output schema means the description should have noted the precondition of a reachable/on console and roughly what comes back. It is minimum viable, not complete.

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?

The tool takes zero parameters and the schema has 100% description coverage, so the parameter baseline of 4 applies. There is no parameter semantics left for the description to add.

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?

States a specific verb ('Fetches') and resource ('the full list of installed games and applications') with source scope ('from the console'), which is clear and unambiguous. It does not differentiate itself from siblings such as xbox_discover, xbox_launch, or xbox_get_config, so it lands at a clear-but-undifferentiated 4.

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 on when to use this versus xbox_discover or xbox_get_config, and no stated prerequisites (e.g., that the console must be powered on or the device authenticated). The agent must infer usage entirely from the name and verb.

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