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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description's job is to add value — and it does: a stable items[] envelope, bounded includes with include.limit capping each, single-page results, and explicit pagination-disclosure behavior. That is meaningful operational context beyond the annotations.

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?

Four tight sentences, front-loaded with the return envelope and then the include behavior before the pagination caveat. Dense but every sentence carries information; 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?

An output schema exists, so return values need not be explained, and the description appropriately focuses on the envelope, include bounding, and pagination semantics. The main gap is filter/limit/cursor semantics, but the structured schema carries those keys adequately.

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 only 17% (essentially just workspaceId and a nested media note), so the description is expected to compensate. It explains the include object's semantics (calendar projection, suggestions, media/full records, analytics, include.limit) but says nothing about ids, limit, cursor, or filters, leaving the list/pagination parameters undocumented in prose.

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+resource ('Read one or many content records'), immediately distinguishing it as a read operation from the mutation siblings edit_content and delete_content. It doesn't explicitly name those siblings as alternatives, but the verb makes the boundary obvious.

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?

Provides real operating guidance (page through before counting, don't present a page as the whole set) and describes what includes add, but never states when to prefer this tool over the edit/delete content siblings or what prerequisites (workspace scoping) select it. Usage is implied rather than explicit.

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