Get PubChem Compound

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

As no annotations are provided, the description carries full burden. It states 'retrieve compound properties', which implies a read-only operation, but provides no additional behavioral details such as authentication, rate limits, error handling (e.g., if compound not found), or whether it returns exact matches only. The description is minimal and adds little beyond the tool name.

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 sentence—concise but unstructured. It lacks front-loading of key information and uses no visual formatting. Every word is necessary, but the structure is minimal.

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 simplicity of the tool (single parameter, no annotations, output schema exists), the description is adequate but not complete. It does not specify whether searches are case-sensitive, if multiple matches are returned, or any limitations. An agent might need additional context for robust usage.

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% as the only parameter 'name' has a clear description with examples. The tool description does not add any further semantic meaning beyond what the schema already provides. According to the rubric, with high coverage, baseline is 3, and the description does not exceed that.

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 verb 'retrieve', the resource 'compound properties from PubChem', and the method 'by name'. It is specific and understandable, but does not differentiate from sibling tools like 'get_chembl_activities' or 'query_drugbank', which also retrieve compound data from other sources.

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 guidance is provided on when to use this tool versus alternatives. The description simply states what it does, leaving the agent without context for choosing among the many similar sibling tools (e.g., search_chembl_compounds, query_drugbank).

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