get_mixture_properties

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

No annotations provided, so description carries full burden. It lists returned properties but discloses no behavioral traits (e.g., read-only nature, rate limits, error behavior). Lacks context like 'does not modify state.'

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?

Description is a single paragraph that concisely lists properties without unnecessary repetition. Could be slightly shorter, but no fluff.

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?

Output schema exists, so description needn't explain return values, but it does anyway. Lacks information on prerequisites, error conditions, or state changes. Adequate but not comprehensive given complexity.

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?

Input schema for 'name' parameter includes a description, so baseline is 3 despite context signal claiming 0% coverage. Tool description adds no additional parameter meaning 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?

Description clearly states the tool retrieves comprehensive thermodynamic and transport properties of a lab bench mixture, listing specific properties. This distinguishes it from siblings like get_species_properties (species-level) and get_reaction_rates (reaction-level).

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?

Description implies usage when mixture properties are needed, but provides no explicit guidance on when to use this tool versus alternatives (e.g., get_species_properties for species-specific data) or prerequisites (e.g., mixture must exist).

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