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

With no annotations provided, the description carries the full burden and does disclose two non-obvious behaviors: results are scoped to the authenticated key's user, and locked saves return locked: true with no contents. It does not cover failure behavior for a nonexistent or foreign calculationId, which is the remaining gap for an unannotated read tool.

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?

Three short sentences, zero padding, with the ownership constraint front-loaded and the edge case last. Every sentence carries distinct information.

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?

An output schema exists, so return values need not be described, and the description still covers ownership scope, call sequencing, and the locked-save edge case. The only omission is error/not-found behavior, which leaves it slightly short of fully complete for a lookup 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?

Schema coverage is 100% and the single parameter's description already says 'ID returned by list_saved_calculations,' so the tool description adds essentially nothing new about the parameter. Baseline 3 applies when the schema fully documents the input.

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 ('Loads') and resource ('one saved calculation') with explicit ownership scope ('belonging to the authenticated API key's user'), which cleanly separates it from list_saved_calculations and compare_saved_calculations. An agent can identify this as the single-item retrieval tool without opening any schema.

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?

Gives an explicit sequencing instruction: 'Use after list_saved_calculations to retrieve full details of a specific saved scenario,' which tells the agent both the precondition and the intent. It does not mention when to prefer compare_saved_calculations or what to do when the ID is unknown, so it stops short of full when/when-not coverage.

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