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

With no annotations, the description carries full burden. It reveals the read-only nature (search) and mentions pricing and public-domain source. However, it does not disclose the cap on returned rows (limit default 25, max 100) or pagination behavior, which are important for agent expectations.

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 two sentences plus a pricing tag, front-loaded with a engaging question. It efficiently conveys data source, filters, outputs, and cost. The opening question, while slightly informal, does not waste space. Could be slightly tighter by removing the question, but it's still effective.

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 9 optional parameters and no output schema, the description covers the key filters and outputs but omits details on sorting, pagination, and default behavior. It mentions limit but does not explain offset or sort semantics. Adequate but not complete for complex queries.

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 coverage is 100%, so baseline is 3. The description adds value by listing filterable fields and noting computed outputs, but it does not elaborate on individual parameter syntax or constraints beyond what the schema already provides.

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 identifies the tool as searching HCRIS S-3 cost reports for staffing metrics. It specifies the data source, available filters (state, CCN, name, etc.), and the exact outputs (FTE, beds, ratios), distinguishing it from generic hospital data tools.

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 provides clear context: it searches flattened HCRIS S-3 records by specified filters. It does not explicitly contrast with siblings like hcris_staffing_decline_search, but the specificity (returning computed ratios) implies its use case for staffing analysis. Lacking explicit when-not guidance prevents a 5.

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