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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is settled and the description is not required to restate it. What the description adds beyond that is thin: "RETURNS: 校验结果" says nothing about whether the result is pass/fail, a list of rule violations, severity levels, or whether it blocks export. No mention of what standards version is applied or of any scoping behaviour.

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 pipe-delimited USE WHEN / ALIASES / RETURNS segmentation is easy to scan and the trigger condition is front-loaded. The opening clause duplicates the tool name and title verbatim, and the alias block is keyword padding rather than information, but neither is harmful.

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 one-parameter, non-destructive read tool with annotations and no output schema, the definition covers the essentials but leaves two real gaps: the meaning of an absent form_id and the shape/behaviour of the validation result. Sibling differentiation is also missing in a catalog of ~130 tools, which raises the cost of choosing correctly.

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 description coverage is 100% and there is a single optional parameter (form_id), so the schema already documents it adequately; the baseline of 3 applies. The description adds no meaning beyond it — notably it never explains what happens when form_id is omitted (validate all CRFs? validate the whole study?), which is exactly the semantic an agent would need.

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?

"check whether CRF data meets CDISC SDTM conventions before export" gives a specific verb (validate/check) and a specific standard (CDISC SDTM), which is more than a name restatement. It does not differentiate from any sibling — the closest neighbours (act_design_export_check, reporting_checklist, data compliance-ish tools) are never named, so an agent must infer the boundary itself.

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 "USE WHEN" clause supplies a concrete triggering condition: pre-export verification of CRF data against SDTM conventions. It does not state when NOT to use it nor point at any alternative for e.g. general reporting compliance, so the routing guidance is clear but open-ended.

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