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

With no annotations, the description must carry the full behavioral burden. It only lists content areas and gives no information about return format, how the facility_type parameter affects the checklist, or whether the tool is read-only. This leaves the agent guessing about the tool's behavior and output.

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 a single, concise sentence that front-loads the core purpose and lists key areas, with no filler or redundant information. Every word adds value.

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?

The tool has an optional parameter that is not explained in the description, and there is no output schema to indicate return structure. The description does not explain how facility_type tailors the checklist or what the agent should expect as output, making it incomplete for confident invocation.

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?

The input schema fully documents the single optional parameter (facility_type) with allowed values in its description, so baseline is 3. The tool description adds no additional context about how this parameter influences the checklist, despite the schema not using enums.

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 clearly identifies the tool as a GMP audit checklist under EU EudraLex Vol.4, listing covered areas (QMS, personnel, premises, documentation, production, QC). It distinguishes itself from sibling tools focused on other regulatory topics, though it lacks an explicit action verb like 'generate' or 'provide' to say what the tool does.

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 implies use for GMP audit contexts via the topic and reference to EU regulations, and the sibling tools cover different domains (e.g., clinical trials, device classification). However, it does not explicitly state when to use this tool versus alternatives or any exclusions, leaving usage to be inferred from the niche topic.

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