get_app

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

No annotations are present, so the description carries the full burden. It discloses that the operation is a fetch (read) and that it targets 'installed' apps, adding a scope constraint. However, it does not explain error behavior, permissions, or return format. This is adequate for a simple read but lacks depth.

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: 'Fetch a specific installed app by ID.' It is concise, front-loaded with the verb, and contains zero waste. Every word earns its place.

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?

The tool is simple with one parameter and no output schema. The description provides enough to understand the core action, but it does not mention return details, alternatives, or any context like permissions. Given no annotations or output schema, a bit more context could be beneficial, but for a simple fetch it is minimally viable.

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 input schema fully documents the 'id' parameter with a clear example. The description only says 'by ID', which does not add new meaning beyond the schema. With 100% schema description coverage, the baseline is 3, and no additional value is provided.

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 action ('Fetch'), the resource ('a specific installed app'), and the scope ('by ID'). This distinguishes it from sibling tools like get_apps (which would list apps) and get_app_proxy, making the purpose unambiguous.

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 implies usage: use this tool when you have an app ID and need a specific installed app. However, it does not explicitly mention alternatives or when not to use it (e.g., for listing use get_apps). No clear exclusion or alternative guidance is provided.

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