get_vaccination_status

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the tool returns data and flags status, but does not address permissions, authentication, rate limits, or any side effects. For a simple read operation this is minimally adequate, but lacks depth.

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 very concise: one opening sentence followed by a bulleted list of use cases. Every sentence adds value and is front-loaded with the main action. Zero wasted words.

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 no parameters and no output schema, the description is complete. It explains what is returned (all recorded vaccinations, with overdue/missing flags) and when to use it. The tool is simple, and the description covers all necessary context for an agent to invoke it correctly.

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?

There are zero parameters in the input schema (schema description coverage 100% trivially). Per guidelines, 0 parameters yields a default baseline of 4. No additional parameter information is needed, and the description does not add any parameter semantics beyond the schema.

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 returns all recorded vaccinations and flags overdue/missing ones, with specific verb 'returns' and resource 'vaccinations'. It distinguishes from sibling tools like get_allergies or get_current_medications by focusing exclusively on vaccination records.

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 lists when to use the tool via bullet points (vaccination history, up-to-date queries, missing/overdue vaccines, travel recommendations). No exclusions or alternative tool names are provided, but the context is clear enough for an agent to select it appropriately.

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