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

Annotations already cover read-only, non-destructive and closed-world, so the description's added value is the pagination contract (advance next_offset until null) and the base64 decoding requirement, both of which the agent cannot learn from annotations. It stops short of noting the bounded-range limits or that the artifact is immutable.

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?

Two sentences, front-loaded with the action and scope, then the pagination protocol. No filler and nothing repeated from the title or schema.

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?

An output schema exists, so return-shape explanation is unnecessary, and auth is touched on. But for a 4-parameter tool with zero schema descriptions, missing pieces remain: the fixed artifact name, the maximum chunk size, and the prerequisite of obtaining task_id via agent_task_result are all left unstated.

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 carry parameter meaning, and it only partially does: 'bounded byte range' implies offset/limit but never explains defaults, the 65536 cap, or that name is constrained to the single literal changes.patch. task_id is referenced only obliquely as 'an authenticated personal-agent task result'.

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?

States a specific verb and resource: read a bounded byte range from an artifact declared by a personal-agent task result. It implicitly ties itself to the agent_task_result family, but never names a sibling it should be preferred over or distinguished from, so the agent must infer the boundary from the resource noun alone.

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 second sentence gives genuine procedural guidance: decode data_base64 and keep paging from next_offset until it is null. However, there is no statement of when to reach for this tool versus agent_task_result or how to obtain a valid task_id in the first place, so the entry condition is only implied.

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