pubchem_properties

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

No annotations are provided, so the description carries the burden. The verb 'Get' implies a read-only lookup, which is a useful behavioral signal, but the description says nothing about rate limits, authentication, or that defaults are applied when properties are omitted.

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 efficient sentence with no wasted words, and the key identifier (CID) is front-loaded. It is appropriately terse for a simple getter, though it could have carried one more clause about defaults without bloat.

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 two-parameter getter this is nearly sufficient, but with no output schema and no annotations the description could usefully state what is returned or that default properties apply when the parameter is omitted. It is adequate but has clear gaps.

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%, so both parameters are already documented in the schema. The description maps 'CID' and 'properties' to the tool's function but adds no syntax, format, or default information beyond what the schema provides, making the baseline 3 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 ('Get') and resource ('specific properties of a PubChem compound') with the identifying key ('by CID'). This is clear, though it does not explicitly name the sibling pubchem_search as the way to obtain a CID, so differentiation is left implicit.

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?

There is no explicit when-to-use or when-not-to-use statement. The phrase 'by CID' implies the prerequisite (you must already have a CID, likely from pubchem_search), which is only an implied usage guideline rather than stated guidance or an alternative.

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