Show App Configuration

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds limited value. It mentions returning a JSON object and the endpoint path. No contradictions, but it does not disclose potential side effects or pagination behavior noted in the schema.

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 mostly concise and front-loaded with the purpose. It contains some redundancy (first two sentences essentially repeat), but overall it efficiently conveys the tool's function and required parameters.

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 GET tool, the description covers purpose and required inputs. However, it lacks details about the response structure, error cases, or explanation of why optional pagination parameters exist. Without an output schema, more context would be beneficial.

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 provides detailed descriptions for all four parameters (100% coverage). The description only reiterates that id and company_id are required, adding no new semantic information beyond what the schema already provides.

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 function: 'Get the details of a single app configuration.' It specifies the verb (get), resource (app configuration), and scope (single, by identifier). This distinguishes it from siblings like list_app_configurations, which retrieves multiple records.

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 provides usage guidance by stating 'Use this to fetch the full details of a specific App Marketplace records by its identifier.' It implies the tool is for single-record retrieval, differentiating from list endpoints. However, it does not explicitly mention when not to use or alternatives.

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