Show App Installation

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only behavior is clear. The description adds that it returns a JSON object and mentions the HTTP GET method via the endpoint, but these are already implied by annotations.

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 concise (5 sentences) and front-loaded with the core purpose. Every sentence provides useful information, including the endpoint and API category. No wasted 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?

The description is fairly complete for a read-only detail retrieval tool. It explains the return type (JSON object), lists required parameters, and provides the API endpoint. However, without an output schema, more detail on the structure of the returned JSON would be helpful.

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 has 100% coverage with descriptions for all 5 parameters. The description repeats the required parameters and the mutual exclusivity of company_id/project_id, which is already in the schema. It does not add new meaning 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 clearly states the tool's purpose: 'Get the details of a single app installation.' It specifies the action (get), the resource (app installation details), and distinguishes from siblings by mentioning 'single app installation' and providing the exact API endpoint.

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 tells when to use it ('fetch the full details of a specific App Marketplace records') but does not provide explicit guidance on when not to use it or mention alternative tools. Given the large number of sibling tools, some exclusion criteria would help.

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