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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that these are 'recorded' nodes scoped to an owned project, which is modest added context, but says nothing about pagination, result size, or ordering.

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 tightly packed sentences with the purpose first and the disambiguation second. No filler, no repetition of the name.

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?

There is no output schema, but annotations cover the safety profile and the description sketches the return shape (nodes and links). However, it ignores the optional sessionId/executionId filters entirely, leaving the agent to infer their effect from a schema whose descriptions for those two fields are erroneous.

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 the schema carries parameter documentation and the baseline is 3. The description adds no meaning about projectId, sessionId, or executionId — notably it doesn't clarify that sessionId/executionId narrow the read, which matters given the schema's copy-paste descriptions for those fields.

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 (recorded Context nodes and their links) and scopes it to an owned project. It also explicitly distinguishes itself from the sibling get_graph_scope, so an agent can route without inspecting 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?

Gives both when to use it ('session reasoning and decisions') and when not to ('not the structural project graph'), naming the alternative tool get_graph_scope explicitly. This is exactly the routing signal an agent needs.

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