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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: cursor semantics, that next_view_id must be fed back as start_view_id, and that it is absent when paging is done. It does not discuss access-control implications of inaccessible_view_ids beyond naming the field.

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 dense sentences, front-loaded with the core action and scope before the pagination mechanics. Every clause carries information an agent needs; nothing is 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, yet the description still summarizes the page payload (view_ids, inaccessible_view_ids, next_view_id) to close the pagination loop. Combined with full annotation coverage and 100% schema coverage, nothing needed to invoke this 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 both optional parameters and their constraints (limit 1–20, default 5; projectId discovery via xtiles_list_projects; start_view_id as cursor) are already fully documented. The description restates the start_view_id/limit pairing without adding syntax or edge-case detail beyond the schema, so the baseline 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 and resource ('Read the combined content of a project') and clarifies the scope as 'concatenated views,' which implicitly separates it from xtiles_get_view_content and xtiles_get_project_structure. It stops short of naming those siblings explicitly, so an agent must infer the boundary.

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?

It gives concrete pagination guidance ('Use start_view_id + limit to page through a large project'), which is implied usage rather than an explicit when-to-use/when-not statement. It never says when to prefer this over xtiles_get_view_content or xtiles_get_collection_content.

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