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

Annotations already declare readOnlyHint and idempotentHint, so the description's 'Read' aligns. It adds value by detailing pagination (skip/take), filtering (tipo), and bulk execution support, which are not captured in annotations.

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 short (3 sentences) and front-loaded with the core action. However, listing multiple actions (list, get, get_latest) when only list is active adds minor redundancy.

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 8 parameters, no output schema, and no enum hints, the description should provide more context on how parameters interact (e.g., difference between patient_id and patient_ids, or anthropometry_id vs. ids). The bulk support is noted, but overall completeness is insufficient.

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?

With 0% schema description coverage, the description must compensate but only briefly mentions 'paginated' and 'filter by tipo' and bulk support with patient_ids/anthropometry_ids. It does not explain each of the 8 parameters individually, leaving gaps.

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 states the tool reads anthropometric evaluations and mentions list with pagination and filtering. It distinguishes from sibling get and get_latest tools by including a 'Flattened action: list' note, though listing multiple actions could cause confusion.

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 description does not explicitly state when to use this tool versus alternatives like get or get_latest. It implies batch usage through bulk support but lacks direct guidance or exclusions.

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