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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds little beyond confirming it is a catalog lookup — no mention of not-found behavior, caching, or scope — which is acceptable given complete 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?

Three tight sentences with the purpose front-loaded, followed by the parameter hint and then the sibling routing. Nothing is redundant or padded.

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 single-parameter read with full annotations and no output schema, this covers what an agent needs to call it correctly, including the slug flexibility. The one gap is that 'metadata' is never qualified — which fields come back is left unknown, though the low-stakes read nature makes that minor.

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?

Schema coverage is 0%, so the description must carry the parameter burden, and it does: it clarifies that appId may be either an ID or a human-readable slug such as 'spotify'. That is real added meaning the bare 'string' schema lacks; it stops short of saying where to obtain a valid ID.

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+resource ('Metadata for one app in the catalog') and the scoping word 'one' distinguishes it from list_apps/search_apps. An agent can tell immediately this is a single-entity lookup, not a search.

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?

Explicitly routes to the sibling get_app_flows for flow data, which gives a clear when-to-use-this-instead signal. It does not say when to prefer list_apps or search_apps over this when the ID/name is unknown, so the exclusion side is only partial.

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