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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered by structured data. The description adds only the category scope and the optional installed-only narrowing; it says nothing about result size, ordering, or pagination for a catalog listing.

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?

A single front-loaded sentence with no filler; the scope comes first and the optional filter second. Nothing redundant with the title or annotations.

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 read-only list tool with no output schema, the description is minimally sufficient but leaves meaningful gaps: what a 'catalog' entry looks like, how teamId affects scope, and whether results are paginated or contain credentials/installation state.

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 description coverage is only 33% (only 'variant' is documented), so the description needs to carry more weight than it does. It hints at the onlyInstalled filter and loosely at variant categories, but never explains teamId scoping or enumerates variant values, leaving two of three parameters ambiguous.

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 ('Browse') and resource ('app catalog') and enumerates the categories the catalog covers (calendars, video, payments, automation), which is more than a restatement of the name. It does not, however, distinguish itself from nearby siblings like list_conferencing_apps or get_app.

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 phrase 'optionally only installed apps' implies a browsing use case with an optional narrowing filter, so intended usage is inferable. There is no explicit guidance on when to use this versus get_app (single app) or the more specific list_conferencing_apps, and no prerequisites are mentioned.

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