gov.osha-accidents

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

The description mentions dataset size but does not disclose behavioral traits like read-only nature, pagination, rate limits, or required permissions. With no annotations provided, the description should carry this burden but falls short.

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 concise with two sentences that effectively front-load the purpose. It is efficient but could be structured with more detail without becoming verbose.

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?

Despite the complexity of 11 parameters and no output schema or annotations, the description only provides result field details. It lacks necessary context for effective tool invocation, such as parameter descriptions and usage constraints.

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 11 parameters with 0% schema description coverage, and the description does not explain any parameter meaning or usage. The only parameter-related info is the list of fields in the results, not the filter/input parameters.

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 returning OSHA-investigated workplace accident reports from the DOL Open Data Portal, listing specific fields and noting a dataset size of ~165k records. This differentiates it from sibling tools like gov.osha-inspections and gov.osha-violations.

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?

No guidance is provided on when to use this tool versus alternatives such as gov.osha-inspections or gov.osha-violations. There are no examples, exclusions, or contextual hints about appropriate use cases.

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