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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description adds useful content characterization (cross-cutting safety principles mapped to framework suites, drawn from real deployments) but says nothing about result volume, pagination, or ordering for a list tool.

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 sentences, front-loaded with the resource and provenance before the filters, with no filler. The final sentence about the normative pattern layer is slightly tangential but earns its place as a disambiguation signal.

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, no-required-parameter list tool with a fully documented two-param schema, the description covers what the data is, where it comes from, and how to narrow it. The absence of any note on return shape or result size is a minor gap given there is no output schema.

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%, so the schema already documents both optional filters; baseline is 3. The description restates the filter intents and adds the example suite IDs ('D3', 'I2') notion via the schema, but notably narrows query scope to 'titles and principles' while the schema says 'titles, principles, narratives' — no meaningful semantic value added 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?

Specific verb (list) plus resource (operational heuristics) with the provenance stated ('distilled from production agentic AI deployment') and an explicit boundary against the sibling pattern tools ('Separate from the normative pattern layer'). An agent can distinguish this from search_patterns/find_patterns_for_task and from get_operational_heuristic (singular) without opening any schema.

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 states the two filter conditions and what each selects ('heuristics relevant to a specific suite', 'keyword search'), giving clear usage context, and it names the excluded category (normative pattern layer). It does not explicitly route the agent to get_operational_heuristic for a single item or state when NOT to use this tool, so it stops short of a full when/when-not/alternatives treatment.

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