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

Annotations already declare this a safe, read-only, idempotent operation; the description adds that it returns the complete graph in canonical order. However, it does not mention pagination/cursor behavior despite cursor and pageSize parameters, and there is no output schema.

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?

A single front-loaded sentence that conveys action, resource, output properties, and use cases with no filler or repetition.

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?

The core action and output ordering are clear, and annotations cover safety, so a basic call with projectId is feasible. But with no output schema and no parameter descriptions, pagination behavior and sessionId semantics remain gaps.

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% and the description names none of the four parameters. Cursor, pageSize, projectId, and especially sessionId are left entirely unexplained, so the description adds no semantic value over the raw schema.

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?

Description uses a specific verb ('Read') and a specific resource ('the published graph'), and adds distinctive output traits ('complete and in canonical node order'). This clearly separates it from sibling tools like publish_project_graph or get_context_graph.

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?

States the intended use cases ('for diffing, resuming, or verifying a mapping'), giving clear context for when to call it. It does not explicitly name alternatives or when not to use it.

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