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

The description adds behavioral context beyond the readOnlyHint/idempotentHint annotations by clarifying the output contents and stating it is 'Educational reference, not medical advice'. This discloses limitations and purpose, which is valuable for an AI agent. There is 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 moderately long but well-structured, front-loading the main verb 'Get a full nursing care plan' and then listing details and usage context. Each sentence contributes meaningful information, though the example conditions are somewhat redundant with the schema.

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 with one parameter and no output schema, the description is comprehensive: it details all expected return sections, target audience, and use cases. The educational disclaimer also addresses potential misuse. This fully equips an agent to decide when and how to invoke the tool.

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 already fully documents the single 'condition' parameter with examples, and the description repeats those examples ('sepsis, CHF, COPD, diabetes, pneumonia or MI') without adding new semantics such as formatting or constraints. Given the schema coverage is 100%, a baseline of 3 is appropriate.

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 retrieves a 'full nursing care plan for a specific condition' and enumerates contents (assessment, diagnoses, goals, interventions, rationales, evaluation, sources). This distinguishes it from siblings like get_nursing_diagnosis, which focuses on a single diagnosis, and list_nursing_conditions, which likely lists conditions.

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 explicitly says 'Use when a nursing student asks for a care plan, nursing diagnoses, interventions, goals or AEB statements for any condition', providing clear context for when to select this tool. However, it does not explicitly mention alternatives or when not to use it, especially relative to the sibling tool get_nursing_diagnosis, so it lacks exclusions.

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