get_hazard_skin_eye

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered externally. The description adds no behavioral context beyond that—no auth requirements, no coverage/pagination notes, no indication of what happens for unknown DTXSIDs.

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?

A single front-loaded sentence with no waste; the verb and resource come first. It is efficient, though so terse that it arguably omits useful routing information rather than trimming filler.

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 single-record lookup with a rich output schema and full annotations, the description is minimally sufficient—the agent knows what it retrieves. Its completeness gap is the lack of any routing against the batch sibling and other hazard summary tools, which is the main decision an agent must make here.

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% for the single dtxsid parameter, so the schema carries full parameter documentation. The description adds nothing about the identifier format or accepted values, which is the baseline 3 expected when the schema does the heavy lifting.

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 gives a specific verb (Retrieve) and resource (skin and eye hazard data) scoped to a single chemical, so an agent knows what comes back. However, it does not distinguish itself from the sibling batch_get_hazard_skin_eye or other hazard tools, so the sibling differentiation required for a 5 is absent.

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, when-not-to-use, or alternative tool is named. The phrase 'for a single chemical' weakly implies a single-record fetch and hints at a batch counterpart, but with batch_get_hazard_skin_eye sitting right there in the sibling list, an explicit routing sentence is needed and absent.

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