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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: 'This reads recorded context, not current local source,' which tells the agent the data may be stale relative to disk. It does not cover scope or pagination of the returned overview.

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 short sentences, zero filler, and the caveat about recorded vs. local source is front-loaded right after the action statement. Every clause earns its place.

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?

For a read-only tool whose annotations already carry the safety profile and with no output schema to explain, the definition covers what is read and a key data-freshness caveat. The remaining gap is the unexplained sessionId/executionId scoping parameters, whose schema text is 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 baseline is 3, and the description adds nothing about projectId/sessionId/executionId semantics. Worse, the schema's own descriptions for sessionId and executionId are copy-pasted from projectId ('Owned project ID returned by list_linked_projects...'), so the description misses a chance to disambiguate what those two optional scoping parameters actually narrow.

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?

The description gives a specific verb and resource ('Read the Context overview for an owned project') and implicitly contrasts it with the 'detailed context graph', which separates it from get_context_graph. It falls short of naming that sibling outright, so the differentiation is inferred rather than stated.

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?

'orient yourself before inspecting its detailed context graph' establishes a clear sequencing context: call this first at a coarse level, then drill in with get_context_graph. No explicit when-not-to-use or alternative is named, so it stops short of a 5.

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