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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description goes beyond them by disclosing the actual payload (ownership category, city, main phone number) and the interpretive takeaway about financial assistance policy, which helps the agent reason about results.

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 first two sentences restate the tool title verbatim, which is redundant given the separate title field. The remaining content is useful and front-loaded, but there is measurable waste at the start.

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 does the work of explaining what comes back (ownership listing, city, phone, financial-assistance implication). For a simple single-record lookup with full schema coverage and read-only annotations, nothing essential is missing.

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?

Schema description coverage is 100%, so all three parameters are already documented in the schema, including the city/state disambiguation hint. The description adds no syntax or format guidance beyond that, so the baseline 3 applies.

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?

Names a specific verb+resource (look up a hospital's ownership status) and states the scope precisely: Medicare-listed ownership classification for financial-assistance purposes. It is clearly distinguishable from siblings like medbillcheck_check_price or medbillcheck_check_whole_bill, which handle bills rather than hospital classification.

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?

Gives concrete trigger questions ("is St. Luke's in Boise a nonprofit?", "does this hospital have to offer charity care?") that tell the agent when this tool applies. However, it never names an alternative tool or states when NOT to use it, so routing among medbillcheck siblings is left partly to inference.

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