query_rcsb_api

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

No annotations are provided, so the description carries the full burden. It mentions it returns a JSON string but does not disclose whether the operation is read-only, any authentication requirements, rate limits, or error handling behavior. For a query tool, these are important 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 well-organized with sections for Args, common endpoints, and Returns. It is reasonably concise given the need to cover a generic tool, though it could be tightened by removing some redundancy.

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 generic tool, the description gives essential usage details and return type, but lacks guidance on error handling, authentication, rate limits, and potential side effects. Since there is no output schema provided, it should also clarify the response structure beyond just 'JSON string'.

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 0%, but the description compensates well by explaining the endpoint format (with examples) and the params as an optional JSON string. It provides common endpoint patterns, giving the agent enough context to construct valid calls.

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's purpose: 'Make a custom query to the RCSB Data API' and positions it as an advanced direct-access tool for any endpoint. This distinguishes it from the specific sibling tools (e.g., get_pdb_entry, get_polymer_entity) by its generic nature.

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 use for advanced/custom queries with 'advanced tool' and 'any endpoint', but does not explicitly state when to prefer this over the more specific siblings or when not to use it. It lists common endpoints but omits guidance on selecting this tool vs. alternatives.

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