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

The description accurately indicates a read-only operation, consistent with annotations readOnlyHint=true, idempotentHint=true, and destructiveHint=false. It adds limited behavioral context beyond the annotations, such as the focus on stale-source status, but no additional side-effect disclosure is needed.

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 concise and front-loaded with the primary action ('Read a saved model snapshot') followed by the key attributes it returns. Every phrase adds value, and there is no redundant or filler content.

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?

As a read operation with an output schema available, the description appropriately avoids detailing return values. It covers the essential purpose and the distinguishing feature of stale-source status, making it sufficiently complete for basic 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?

The schema provides no description for project_id or scenario_id, and the description does not compensate by explaining how these parameters relate to the scenario lookup. The parameter names are somewhat self-explanatory, but with 0% schema description coverage, the tool description should provide more semantic guidance.

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 'Read' and specifies the resource: a saved model snapshot, including its inputs and stale-source status. This distinguishes it from list-oriented tools like sparkclose.list_scenarios.

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 usage for inspecting a single saved scenario, but it does not explicitly mention when to prefer this over alternatives such as sparkclose.list_scenarios or sparkclose.save_scenario. The context is clear enough for basic direction but not fully explicit.

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