Read artifact

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

With no annotations provided, the description carries the full disclosure burden, and it does add meaningful behavioral context: it reveals that only a bounded prefix is returned (not the whole artifact) and that reading is the intended behavior. However, it stays quiet on what happens at the bound (truncation vs. error), response format, or whether there's pagination.

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 optimally sized at two short sentences with the action front-loaded. The first sentence states precisely the core functionality; the second provides essential operational guidance without redundancy.

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 read-by-ID operation with a flat parameter list and simple output schema, the description adequately covers the essentials. It clearly states the tool's purpose, the nature of the read (bounded prefix), and the strategic preference for its use. It could be enhanced by touching on error behavior or offset/pagination options, but these are not required for basic operability.

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 0% (no parameters documented in the description), so the description must compensate. The phrase 'bounded prefix' conceptually maps to maxBytes, giving that parameter implicit meaning, but the description doesn't explicitly explain any of the three parameters' nuances or tradeoffs.

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 uses a specific action verb ('Read'), identifies the exact resource ('artifact'), and adds critical scoping flavors: 'bounded prefix' and 'by ID'. It clearly distinguishes itself from siblings like artifact_put and communicates that this operation performs a scoped, targeted read rather than a full load.

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 phrase 'Prefer targeted retrieval over loading full artifacts' implies when to use this tool—for bounded, targeted reads—but stops short of naming explicit alternatives or exclusions. The usage context is implied by this guidance, but no sibling tool is directly mentioned as an alternative.

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