get_results

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

No annotations provided, so description carries full burden. It discloses that results are final, may be empty if none, and are only available after job completion. Could mention mutability or side effects, but none expected.

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?

Single sentence with list of result types is efficient and front-loaded. Minor improvement possible by separating examples into a bulleted list.

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?

Lists result types despite no output schema and gives timing condition. Missing failure behavior or clarification that no results means job might not have produced them. Adequate for a simple retrieval tool.

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?

Single parameter 'job_id' has no schema description coverage. Description adds no extra meaning beyond the schema's title 'Job Id'. Baseline for 1 param with 0% coverage is acceptable but uninspired.

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 it returns final job results (NEB barrier/energies, phonon frequencies/stability) and uses specific verbs 'Return' and 'None until job finishes', distinguishing it from siblings like get_status or get_trajectory.

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?

Implicitly indicates usage after job completion via 'None until the job finishes', but does not explicitly state when not to use or compare to alternatives like get_status.

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