Get app details

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

readOnlyHint=true already establishes this as a safe read. The description usefully adds the scope of the return payload (versions, build status, release state), but says nothing about permissions, App Store Connect auth requirements, or rate limits.

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?

One front-loaded sentence that states the resource first and the returned fields second, with no filler. Slightly lean for the amount of behavior it could have covered, but nothing is wasted.

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 low-complexity, read-only lookup with full schema coverage and no output schema, listing the returned fields is the right level of detail. Missing only edge-case behavior (e.g. what happens for an unknown or inaccessible app_id).

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?

Single parameter with 100% schema description coverage, including a format pattern and a pointer to list_apps, so the schema carries the semantics. The description adds no additional meaning about app_id, which is the expected baseline at full coverage.

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?

Specific verb ('Get') plus resource ('app') and an enumeration of what the detail payload covers (versions, build status, release state). It is clear what the tool returns, though it never contrasts itself with siblings like list_apps or release_version.

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 gives no when-to-use or when-not-to-use guidance and does not name an alternative tool. The only steering ('use list_apps to find it') lives in the app_id schema description, not in the tool description itself.

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