list_species_in_mechanism

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

With no annotations provided, the description must disclose behavior. It states 'list all species', which implies a read-only operation with no side effects. This is transparent enough for a simple listing tool, though it could explicitly mention that it does not modify data.

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 a single, clear sentence with no superfluous information. It earns its place by being highly concise.

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?

Given the tool's simplicity (one parameter, existing output schema), the description is mostly adequate. However, it does not clarify what constitutes a 'mechanism file' (e.g., path, content) or that the mechanism must be pre-loaded, leaving minor ambiguity.

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 tool description does not elaborate on the parameter beyond repeating that it is a 'Cantera mechanism file'. The input schema has 0% description coverage for the top-level 'params' property, and the description does not compensate by explaining the parameter's format, constraints, or accepted values.

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 uses a specific verb ('List') and resource ('species defined in a Cantera mechanism file'), clearly distinguishing it from siblings like 'list_available_mechanisms' which lists mechanisms, not species.

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 the tool is used to list species from a mechanism file but provides no explicit guidance on when to use it versus alternatives like 'get_species_properties' or 'check_species_availability'. No when-not-to-use context is given.

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