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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that each item carries its problem class and related records, which is useful behavioral context, but it says nothing about pagination, ordering, result volume, or whether the catalog is complete or curated.

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 dense but well-formed sentence with the resource front-loaded and the example parenthetically placed. Nothing is wasted, though the trailing 'each with its problem class and related records' slightly crowds the core statement.

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, zero-required-parameter list tool with no output schema, the description covers what is returned and roughly its shape. It is missing what an agent would need for practical use — whether results are paginated, how many are returned, and how this differs from get_pattern.

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 100% and the single locale parameter already documents its enum values and the English-fallback behavior. The description does not mention locale at all, so it adds no meaning beyond the schema; baseline 3 applies.

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 names a specific resource — reusable build patterns that prevent Copilot Studio friction — and gives a concrete example (async continuation for the 100-second flow limit), so the agent knows what the tool returns. It is clear but does not explicitly distinguish itself from the sibling get_pattern, which presumably returns a single pattern.

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?

Usage is only implied: 'All' patterns suggests a catalog-wide listing, complementing the singular get_pattern sibling. There is no explicit statement of when to prefer this over get_pattern or list_frictions, and no noted prerequisites or exclusions.

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