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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's job is to add what they can't: it discloses an ownership/authorization requirement and that the call returns the complete JSON, which is essential for an agent with no output schema. Minor gaps remain on error behavior for missing/foreign ids.

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?

One sentence, no filler, with the operation front-loaded and the qualifier ('owner only') placed last where it reads as a caveat. Nothing to trim.

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 single-parameter read tool with no output schema, the description supplies the two things an agent most needs: the access restriction and the fact that the entire model JSON comes back. Only failure modes and id provenance are unaddressed.

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% with a single required 'id' parameter already documented as "Saved model id". The description only restates "by id" without adding format, prefix, or sourcing guidance (e.g., where ids come from), so baseline 3 applies.

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 and resource ("Load ... saved models") plus the retrieval mechanism (by id) and the return shape (full JSON). It implicitly separates itself from save_model/stash_model/list_models, but never names an alternative explicitly.

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 "owner only" phrase gives an access condition, which is a real usage constraint, but the description never says when to prefer this over list_models or get_template, nor what to do if the id is unknown. Usage context is implied rather than spelled out.

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