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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: pagination semantics (limit/offset/total) and, importantly, that long fields are truncated at ~800 characters with a marker, which an agent would otherwise not expect from a read tool.

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?

Three dense sentences, all front-loaded and each carrying distinct information (ordering rationale, pagination, truncation, id source). Packed but not padded; only minor cost is that several facts are compressed into the first sentence.

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?

No output schema exists, and the description compensates by describing the returned shape: a page of items, the `total` count, and truncation of long fields. Combined with the schema's full parameter coverage, an agent has everything needed to call and interpret the result.

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 100%, so limit, offset, datasetId and the workspace quirk are already documented at 100% fidelity in the schema. The description restates limit's default and offset semantics without adding format or edge-case detail, so the baseline of 3 applies.

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 (read) and resource (one Caliper dataset with a page of its items), immediately distinguishing it from caliper_datasets_list, which returns datasets rather than items. An agent can pick between the two without opening either schema.

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?

Explicit sequencing guidance: read this BEFORE editing items because caliper_datasets_update_item needs the item id, and before extending coverage to avoid adding duplicate cases. It also names caliper_datasets_list as the source of the required datasetId, which is the only prerequisite.

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