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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description contributes one extra behavioral fact — that results are privacy-filtered — which is genuinely useful (some content may be redacted), but it says nothing about return shape or size limits.

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?

It is a single sentence, but the sentence is malformed ("Read hosted get graph wiki") and conveys almost no actionable information, so brevity here is under-specification rather than economy.

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 tool with no output schema, the description should at least say what the wiki entry contains and how it relates to the published graph. Annotations cover the safety profile, but the purpose and return content remain opaque, and the garbled wording leaves the agent guessing.

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 baseline is 3. The description adds nothing about the parameters, and it cannot compensate for the schema's own defect that sessionId and executionId carry copy-pasted descriptions referring to a project ID.

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 phrase "Read hosted get graph wiki" just restates the tool name in garbled form rather than describing the resource or what is returned. "Using privacy-filtered project metadata" adds a hint of scope but the agent still cannot tell what a "graph wiki" is or how it differs from siblings like knowledge_read, graph_read, or request_node_explanation.

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 when-to-use guidance and no named alternative, even though the schema itself points at get_roots and get_graph_scope for node discovery. The agent gets no indication of when this read is preferable to the many other read tools in the sibling list.

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