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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint:false, which cover the safety profile. The description adds the vague phrase 'mandate rails', which suggests authorization constraints but does not explain what that entails. No contradiction with annotations, but the behavioral disclosure beyond annotations is minimal and unclear.

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 concise sentence, front-loaded with the core action. However, the phrase 'through Toofi agent-native mandate rails' is jargon that adds little and could confuse. It is efficient but slightly flawed due to unnecessary vague wording.

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?

With 9 optional parameters, an output schema, and rich annotations, the tool is reasonably specified structurally. However, the description does not explain the mandate context, when certain parameters are needed (e.g., mandate_id optional in demo mode), or how this differs from sibling tools. Thus it is adequate but incomplete for an agent to fully leverage it.

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%, so the schema already documents all parameters. The description adds no semantic value to parameters; it does not explain how 'mandate rails' relates to fields like mandate_id, clinic_id, or agent_id. Baseline of 3 applies because the schema carries the full burden.

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 core action: 'List clinic patients' — a specific verb with a resource. It implies distinction from demo tools like list_demo_patients via the word 'clinic', but does not explicitly name alternatives. The trailing phrase 'through Toofi agent-native mandate rails' is vague but does not obscure the primary purpose.

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 guidance is provided on when to use this tool vs. alternatives such as list_demo_patients, get_patient, or list_plans. The description does not mention context, exclusions, or required conditions like mandate scope. The word 'clinic' hints at production use, but this is not explicit.

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