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 fully covered. The description adds only 'RETURNS: PK/PD 评估结果', which conveys no behavioral content — no indication of what analyses are run, what inputs are assumed, or what the result contains.

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 content is a pipe-delimited keyword block with title, USE WHEN, ALIASES, and RETURNS fields. The ALIASES list is retrieval-oriented stuffing that does not help an agent decide or invoke, and the remaining prose is thinner than the boilerplate around it.

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 whose main parameter is a free-form nested object and which returns a report with no output schema, the description should indicate which PK parameters are expected (e.g., CL, V, dose, route) and what an assessment yields. Instead only a title/keyword header is provided.

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% for the two top-level parameters, so the baseline is 3. The description adds nothing beyond the schema, and notably the nested 'pk_params' object is an untyped bag with no inner property definitions — the description does not compensate for that opacity.

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 'USE WHEN' clause names a verb+domain ('pharmacokinetic/pharmacodynamic assessment and dose projection'), which advances slightly past the name, but it never says what an assessment produces or how it differs from closely related siblings such as pk_nca, pkpd_simulate, and species_dose_convert. 'PK/PD 评估' largely restates the tool name.

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?

There is an explicit when-to-use trigger ('pharmacokinetic/pharmacodynamic assessment and dose projection'), which is more than most definitions offer. But no exclusion or alternative routing is given, and in a toolset containing pk_nca, pkpd_simulate, and renal_dose_adjust an agent has no basis for choosing this one.

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