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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds a small amount of context by indicating the graph is 'hosted' and that the data comes from 'privacy-filtered project metadata,' but it does not disclose return format, error behavior, or how optional identifiers affect results.

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?

The description is a single sentence with the main verb front-loaded and no filler. It is concise, though the redundant 'get' in 'hosted get context graph' makes it slightly less polished than it could be.

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?

With no output schema, the description should convey what the tool returns, but it only names 'context graph' without defining its shape or contents. The optional sessionId and executionId parameters are also left unexplained, so an agent has insufficient context for correct invocation.

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%, so the description must compensate, but it only vaguely references 'privacy-filtered project metadata.' It does not explain what projectId, sessionId, or executionId mean, nor how they relate to the graph being retrieved.

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 uses an explicit verb ('Read') and names a specific resource ('hosted ... context graph'), so the core operation is identifiable. However, the phrasing is awkward ('hosted get context graph') and it does not distinguish this tool from sibling read tools such as graph_read or get_context_overview.

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?

There is no guidance about when to prefer this tool over alternatives, no exclusions, and no context about which sibling tools cover similar graph-reading tasks. The phrase 'using privacy-filtered project metadata' hints at a use case but does not provide decision criteria.

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