reunion_get_covid_hospital_stats

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

No annotations are provided, so the description carries the full burden. It discloses the data source (Santé publique France via data.regionreunion.com), sorting order (most recent first), and the specific metrics returned, adding significant context. It does not mention authentication requirements or error handling, but for a read-only data retrieval tool, this is adequate.

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 dense paragraph but is concise and front-loaded with key information. It could be improved with structured lists, but it avoids fluff and earns its place.

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 no output schema, the description adequately explains the return values (list of metrics and sex breakdown) and sorting. It does not detail pagination or empty result behavior, but the limit parameter covers pagination. Overall, it provides sufficient context for typical use.

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 100% description coverage for all 4 parameters, so the description adds no extra parameter-level meaning. The baseline of 3 is appropriate; the description's listing of metrics provides context about what data is returned but does not enhance parameter semantics directly.

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 explicitly states the tool provides daily in-hospital COVID-19 indicators for La Réunion, listing specific metrics (occupied beds, ICU beds, discharges, deaths, new admissions, etc.) and sex breakdown, clearly distinguishing it from the sibling tool reunion_get_covid_emergency_stats.

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 states when to use this tool (for in-hospital stats) and directs users to reunion_get_covid_emergency_stats for ER and SOS Médecins data, providing clear alternatives.

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