check_ctd_completeness

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

In the absence of annotations, the description must disclose behavioral traits. It states it 'identifies gaps' but does not describe side effects, return format, or whether the tool is read-only. For a validation tool, this is moderately transparent but lacks specifics.

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 with no unnecessary words or complexity. It efficiently conveys the tool's purpose without fluff.

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 tool with three parameters, no nested objects, and no output schema, the description should at least hint at the return format (e.g., list of missing sections). It does not, making the contextual information slightly incomplete.

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 100% with descriptions for all three parameters. The description adds no additional parameter-level details beyond restating the purpose. Baseline score of 3 applies as schema does the heavy lifting.

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 specifies the action ('Check a list... against required sections and identify gaps') and the resource (CTD sections). It effectively distinguishes from sibling tools like check_ich_compliance (ICH focus) and map_ctd_section (single section mapping).

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?

No explicit guidance on when to use this tool versus alternatives such as check_ich_compliance or generate_submission_checklist. The description implies a scenario (having a list of sections) but does not provide exclusions or context for when not to use it.

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