get_artifact_chunk

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

With no annotations provided, the description carries the full burden, and it delivers substantial behavioral detail: base64 chunk decoding, SHA-256 verification against the export manifest, UTF-8 concerns when chunks split multibyte characters, response_complete scope, eof/next_offset semantics, and the upstream composite/atomicity caveat.

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 opens with a crisp summary and follows with dense but purposeful sentences. Every sentence contributes necessary semantics: provenance, decoding, verification, pagination, and a caveat about upstream completeness. There is no filler.

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?

Despite having no annotations and only a bare input schema, the description gives an agent a complete mental model: how to obtain the artifact_id, how to assemble the artifact, how to verify correctness, how to know when the artifact ends, and what limitations exist. An output schema exists to cover return values, so the description does not need to repeat them.

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. It adds meaning for artifact_id by explaining it is opaque and comes from export_activity_data, and it implies offset/max_bytes through the byte-range and chunk language. However, it never explicitly defines offset and max_bytes in terms of byte positions, limits, or defaults, so the compensation is incomplete.

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 opening sentence states a specific verb, resource, and scope: 'Read one verified byte range from a temporary activity export.' This clearly identifies the operation and distinguishes it from sibling tools by referencing the opaque artifact_id and the chunk/byte-range model.

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 explicitly tells the agent to use the artifact_id returned by export_activity_data member, and explains that response_complete, eof, and next_offset signal progress through the artifact. It does not explicitly contrast this tool with alternatives or say when not to use it, so it stops short of a 5.

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