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

Annotations already declare readOnlyHint true, idempotentHint true, and destructiveHint false, and the description's 'Read' is consistent with these. It adds one behavioral clue beyond annotations: the result is based on 'privacy-filtered project metadata,' which suggests output filtering, but it does not mention pagination, limits, or return behavior.

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 compact sentence with no filler, which is good, but the phrasing 'hosted get graph scope' is unclear and the sentence does not organize information effectively. It is concise without being sufficiently informative.

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?

Given six parameters, no output schema, and zero schema description coverage, this one-sentence description is not enough for an agent to know what the tool returns or how to correctly form a request. The annotations cover safety, but not invocation semantics or response expectations.

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 needed to compensate, but it explains none of the six parameters. Required projectId and nodeId are implied only by the tool name and schema, and cursor, pageSize, sessionId, and executionId are completely unexplained.

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 states a read operation on a 'graph scope' resource, which is more than a tautology and distinguishes it as a read operation. However, 'hosted get graph scope' is awkward and never defines what a graph scope is or how it relates to sibling tools like get_context_graph, get_graph_wiki, or graph_read.

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?

No guidance is provided about when to call this tool instead of the many similar read/graph tools in the sibling list. The description implies a generic read scenario but gives no conditions, exclusions, or alternatives.

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