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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds real behavior — cursor chaining via next_view_id, termination when it is absent, and the inaccessible_view_ids surface. It does not discuss any auth/permission requirements, but for a read tool that is a minor gap.

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?

Front-loaded with the core purpose in sentence one, then pagination mechanics, then the description-tag visibility rule. Dense but every sentence carries information; the final clause about collection-page descriptions is complex but not 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 needn't be spelled out, and the description still covers pagination protocol, the inaccessible-view case, and the description-tag visibility semantics. Nothing an agent needs to page correctly is missing.

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 coverage is 100%, so baseline is 3; the description goes beyond the schema by explaining the cursor contract (take next_view_id and pass it back as start_view_id) and the limit-1 pattern for single-page reads, which the schema does not convey.

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 (combined content of a project = concatenated views), and separates itself from siblings by naming xtiles_get_view_content as the single-view alternative. An agent can distinguish this from get_collection_content, get_content_by_link, and get_view_content without opening schemas.

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?

Explicitly says how to page (start_view_id + limit) and routes the agent to xtiles_get_view_content for reading a collection page on its own, plus the limit-1 trick here. Clear context, though it does not state when NOT to use this versus get_collection_content or get_content_by_link.

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