get_chemicals

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

With no annotations provided, the description bears the full burden. It adds a 'tier: readonly-owner' hint and the endpoint mapping, indicating a read-only operation with potential owner-level access. However, it does not disclose authentication specifics, error behavior, side effects, or the exact structure of returned records, leaving notable gaps.

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 one succinct sentence followed by the endpoint mapping and tier notation. Every segment contributes value (what, limit, endpoint, access level) and is immediately front-loaded. It is highly concise without waste.

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 (single parameter) and the description captures its core purpose, but it lacks details about the return format ('full records' content), pagination, error handling, and differentiation from search_chemicals. Since there is no output schema, such context would be valuable to make the description fully complete.

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 defines 'chemicalIDs' as an array of numbers with no description and 0% schema coverage. The description compensates partially by stating 'up to 1000 IDs', which clarifies the maximum array length and that elements are IDs. However, it does not explicitly state these are chemical IDs or provide format details beyond the schema.

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 states the tool retrieves full chemical/product records for up to 1000 IDs, using a specific verb and resource. It also maps to the underlying endpoint, which removes ambiguity. This distinguishes it from sibling search tools by focusing on direct ID-based retrieval.

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 implies usage when IDs are available ('up to 1000 IDs') and the tool is read-only, but it does not explicitly state when to use this versus the sibling search_chemicals tool or other searches. No exclusions or alternative tool names are provided, so guidance is only implied.

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