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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered elsewhere. The description adds only the scope boundary (field-level, not term-level), and says nothing about what a suggestion looks like, whether it is advisory versus enforceable, or how partial or ambiguous field lists are handled.

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?

It is short and the scope restriction is front-loaded at the end of a single dense sentence, but the missing punctuation between title fragment, user-question trigger and scope clause makes it read as a stitched-together string rather than structured prose. No sentence is wasted, but the structure harms scanability.

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 single-parameter, read-only advisory tool with no output schema, the definition covers trigger, scope and exclusion adequately. The remaining gap is that it never indicates the shape of the advice returned, which matters since there is no output schema to fall back on.

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 the schema already explains the fields array, including that object-array input is accepted. The description adds no parameter meaning of its own beyond the example field names implied by the AE/CM mention, so the baseline 3 applies.

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 names a specific verb+resource: giving CRF field classification advice (which fields are AE/CM, which dictionary to use, coding level). It also bounds scope by excluding term-level coding. However, the opening repeats the title verbatim and the text is a run-on with no separation between title, trigger, and scope, so the purpose is clear only after parsing.

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?

It states a concrete trigger ('用户问 CRF 字段该怎么编码、要不要用 CDASH MedDRA/WHO-DD') and an explicit exclusion ('不含术语级编码'), which is genuine when-not guidance. It does not point to any alternative tool for the excluded term-level coding case, so routing is implied rather than complete.

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