read_artifact

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 usefully reveals that the tool returns a bounded base64 chunk, implying read-only chunked access. However, it does not explain offset/length boundary behavior, what happens on invalid handles or out-of-range reads, or the role of command_id and idempotency_key.

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 tight sentence with no filler. It front-loads the core action and result. It falls slightly short of 5 because the brevity leaves important parameter and usage context unaddressed, though that trade-off keeps the sentence highly readable.

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 tool with 5 parameters, no annotations, and zero schema description coverage, the description is not complete enough. It does not explain how chunking works with offset and length, how to read the entire artifact, what the output schema contains, or what error conditions exist. The output schema is marked as present, which mitigates return-value documentation, but the missing parameter semantics and chunk iteration details remain significant gaps.

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%, but the description only adds meaning for 'base64 chunk' and indirectly implies offset/length via 'bounded'. It does not document the meaning of handle, length, offset, command_id, or idempotency_key, so the agent must infer most parameter semantics from argument names alone.

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 ('Read'), resource ('managed artifact'), and a precise mode ('one bounded base64 chunk'). This makes the tool's function immediately clear and distinguishes it from the sibling artifact tools like get_artifact_info, delete_artifact, and cleanup_artifacts.

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 gives no context for when this tool should be used relative to alternatives, how to iterate over chunks, or when get_artifact_info might be more appropriate. There is also no mention of prerequisites such as needing a valid handle to an existing managed artifact.

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