List procedures

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

Annotations already declare readOnlyHint and idempotentHint, so the description does not need to add safety info. The description adds that the tool returns outcomes/follow-up dates, which is useful but does not mention pagination or filtering behavior (e.g., via limit, since, until). No contradiction with 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 a single sentence with no filler, but it could be expanded to include parameter info without being overly verbose. It is adequately concise but at the cost of completeness.

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 the tool has 4 optional parameters and an output schema, the description should explain parameter semantics and how to filter. It lacks this information. Additionally, with many siblings, differentiation is missing, making the description incomplete for effective selection and use.

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?

Input schema has 0% description coverage for parameters, so the description must compensate. However, it provides no explanation of the four parameters (user, limit, since, until), leaving their purpose unclear. This is a significant gap.

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 lists 'procedures, surgeries, and tests with outcomes/follow-up dates,' which identifies the resource and action. However, it does not distinguish this tool from many similar list_* siblings, leaving ambiguity about when to use this versus other list tools.

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. Given numerous sibling list tools, the description should indicate that this is for procedure records and not for other record types, but it does not.

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