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

Annotations already declare readOnly and idempotent, and the description adds helpful behavioral context by stating it returns a readiness score and next steps. The 'rapid' qualifier also signals it is not a comprehensive assessment, providing useful transparency beyond the annotations.

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?

Two sentences, front-loaded with the core purpose, concise and free of fluff. Every sentence earns its place by covering scope, output, and escalation.

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 description covers purpose, scope (articles), return value, and escalation path, which is sufficient for a read-only assessment tool with well-documented parameters. The vague 'linked form' reference and lack of detail about how the score is presented are minor gaps.

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?

All 7 parameters have full schema descriptions (100% coverage), so the description does not need to elaborate. It provides no additional parameter guidance beyond the articles referenced, but the schema already carries the semantics, so the baseline 3 is appropriate.

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 states a specific verb ('gap analysis') and resource ('EU DORA'), and distinguishes itself from siblings by focusing on readiness assessment rather than plan generation or framework exploration. The coverage of specific articles (11, 26, 27) makes the scope unambiguous.

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 frames it as a 'rapid' check and explicitly directs users to a linked form for full assessment, establishing when to use it versus escalating. However, it does not explicitly reference sibling tools or list exclusion criteria, so it is not a full when-to-use/when-not-to-use guide.

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