enabiz_list_hospital_visits

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

Description adds behavioral details beyond annotations: requires authenticated session (auth_required error), returns truncated flag, default limit 50, case-insensitive query, and summary fields. No contradictions 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?

Description is concise and well-structured with bullet points. First sentence states purpose, followed by parameter details. No wasted words; appropriate length.

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?

Complete coverage for a list tool with 4 optional parameters. Includes auth requirements, default behavior, filter mechanics, limit, and return indicators (truncated flag). Output schema exists but not needed due to comprehensive description.

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?

All 4 parameters are fully explained in the description despite 0% schema coverage. Describes start_year/end_year range defaults, query as case-insensitive filter, and limit with default value.

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 hospital visits (examinations) by year range, using a specific verb and resource. It distinguishes itself from sibling tools that list other entities like appointments or diagnoses.

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?

Provides explicit guidance on default year range, optional query filter, and limit parameter. Does not explicitly state when not to use, but context from sibling tools suggests this is the appropriate tool for listing visits.

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