Discover QA profiles and bundles

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false. The description adds useful context beyond them: the catalog is static and comes from the installed server's bundled definitions, active sessions and configured models do not change it, and task-type recommendations are shortlists rather than restrictions.

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 front-loaded with the purpose, then moves into usage conditions, cross-references, and a final caveat. The bullet list for related tools is efficient and nothing reads as filler.

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 zero-parameter, read-only discovery tool with an output schema, the description provides everything an agent needs: what it returns, when to call it, what preconditions are unnecessary, and how it relates to sibling tools. Return-value details are appropriately left to the 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?

There are zero parameters, so the rubric baseline is 4. The description adds a small amount of useful clarity by stating that no session or arguments are required, though there is no parameter syntax or structure to explain further.

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 and resource: reading the static profile/bundle catalog, with its contents enumerated (specialists, review scopes, ordered routes). It is clearly distinguishable from siblings like prepare_qa_orchestration and start_qa_orchestration because it describes discovery, not session mutation.

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 says to use this before creating a session or choosing its triage route, and notes that no session or arguments are required. It also provides next-step alternatives for detailed checklists, session creation, route setting, and listing session IDs, and explains how to choose a bundle versus a single profile.

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