get_accident_cases

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the data source and scope but fails to explain what 'aggregated' means, whether the tool returns a list or single record, or any performance or access characteristics. This vagueness leaves the agent unsure what to expect on invocation.

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 brief and front-loaded with the core resource context, followed by a clear usage sentence. It wastes no words, though the first sentence is a fragment rather than a complete statement.

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?

For a simple tool with no output schema and no annotations, the description provides the necessary selection context (source, scope, when to use) but lacks information about the return format or any aggregation semantics. It is minimally adequate but leaves gaps in expected output.

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 0%, and the description does not mention the 'lang' parameter at all. The schema itself provides an enum but the description adds no guidance on how or why to set the language, nor does it compensate for the lack of coverage.

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 resource (Japanese Consumer Affairs Agency accident-database entries for hydrogen inhalation devices) and distinguishes it from sibling tools focused on papers and safety notes. However, it lacks a strong verb, using the noun phrase 'Aggregated record' instead of an action like 'retrieve' or 'list'.

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 explicit when-to-use guidance: 'Use when the user asks about hydrogen device safety incidents.' It does not mention alternative tools or exclusions, but the context is clear and sufficient.

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