conformity_assessment_roadmap

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

With no annotations, the description carries full burden and exceeds expectations, detailing side effects (read-only), authentication, rate limits, error handling, idempotency, and data privacy. This is comprehensive and transparent.

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 lengthy but well-structured with clear headings and bullet points. The first sentence effectively front-loads the purpose. Minor redundancy in the behavioral section could be trimmed without losing 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?

Given the tool's complexity and existence of an output schema, the description covers all essential aspects: purpose, usage, behavior, parameters (though weak). It addresses authentication, rate limits, and data privacy, leaving minimal gaps except parameter semantics.

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 coverage is 0%, but the description's 'Args' section merely restates parameter names and types without adding constraints, examples, or semantic detail. For product_class, it says 'The product class to analyze or process,' which is too generic to be helpful.

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 states 'Produce a conformity assessment roadmap for CE marking your product under CRA,' clearly identifying the verb (produce), resource (roadmap), and context (CE marking). This distinguishes it from siblings like audit_annex_i or classify_product.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance: use for compliance assessment, gap analysis, readiness checks; not as legal advice. This effectively differentiates from alternatives.

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