get_hazard_pprtv

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

Annotations already cover read-only, idempotent, open-world, and non-destructive traits, lowering the bar. However, the description adds no behavioral context whatsoever—nothing about what kind of data PPRTV contains, whether authentication is needed, or any limitations.

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?

One short sentence with no wasted words, front-loaded with the verb and resource. It is appropriately concise, though arguably too minimal to be maximally useful given the tool's context.

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?

The tool is simple (one required parameter), has an output schema, and annotations cover safety. The description is minimally sufficient to invoke it, but it does not explain the obscure 'PPRTV' acronym or provide any routing context among dozens of sibling hazard tools.

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%, and the single parameter (dtxsid) is already documented in the schema as a chemical identifier. The description does not mention the parameter or add any usage detail beyond what the schema provides, so the baseline of 3 is appropriate.

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?

States a specific verb ('Retrieve') and resource ('PPRTV hazard data') for a chemical. The resource name is unique among siblings, so an agent can differentiate it, but the description does not explicitly say how it differs from other hazard endpoints like toxval or iris.

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 when-to-use guidance, no alternatives, no prerequisites. The description merely states the retrieval action without indicating when PPRTV data is the right choice versus the many other hazard tools.

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