baseline_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the output format (PNG) but doesn't disclose what happens if the named baseline doesn't exist, whether the image is returned inline or as a reference/URL, or any error behavior. For a retrieval tool, this is a meaningful gap.

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 a single, efficient sentence that front-loads the action and output format. It earns its place with no filler, though it could add a brief usage hint without becoming bloated.

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 simple one-parameter retrieval tool, the description is nearly adequate, but it lacks error semantics and parameter clarification. With no annotations and no output schema, the agent has no way to know what a failure looks like or how the PNG is delivered. Sibling tools like baseline_list suggest a discovery workflow that isn't mentioned.

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%, so the description must compensate for the undocumented 'name' parameter. The description says 'reference image' but doesn't explicitly state that 'name' is the baseline identifier, nor does it clarify the expected format (e.g., exact name vs. partial match). The agent can guess from the tool name, but the description adds no parameter-level meaning.

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 states a specific verb ('Returns') and resource ('a reference image as PNG'), and the purpose is clear: to fetch a baseline image for visual comparison. It doesn't explicitly distinguish from sibling tools like baseline_list, but the action is distinct enough that an agent can infer the difference.

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?

No guidance is given about when to use this tool versus alternatives. The description doesn't mention that baseline_list should be used to discover available baselines first, nor does it explain when a reference image is needed. The agent must infer usage from the tool name and sibling context.

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