list_care_plans

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

With no annotations, the description must carry behavioral disclosure. 'List' implies a safe, read-only operation, and 'for the launch patient' adds scoping, but it does not mention pagination, result ordering, filtering, or any edge-case behavior. This is adequate for a simple list but not rich.

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, focused sentence with no filler. It communicates the core purpose and scope efficiently, making it easy for an agent to parse.

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?

This is a simple list tool with an output schema, so return-value structure is likely covered elsewhere. However, the unexplained `practice` parameter and lack of any relationship between practice and the launch patient are notable gaps that prevent the description from being fully self-sufficient.

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?

The input schema has one required parameter, `practice`, at 0% schema description coverage. The description does not mention or explain `practice` at all, leaving the agent to guess what value to provide and how it relates to the 'launch patient'. The description fails to compensate for the missing parameter documentation.

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 action ('List'), the resource ('CarePlan resources'), and the scope ('for the launch patient'). This distinguishes it from sibling list_* tools that target other resource types, so an agent can immediately tell when this tool is relevant.

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 gives clear context for when to use this tool: when the launch patient's CarePlan resources are needed. It does not explicitly name alternatives or exclusions, but the scope is specific enough to guide selection among the many sibling tools.

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