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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'privacy-filtered' aspect, which hints at data transformation but does not explain behavior like return format, error conditions, or authentication. No contradiction exists, but the added context is minimal.

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 and not verbose, which is good for conciseness, but it is under-specified rather than efficient. It does not front-load essential information; it simply restates the tool name in a slightly expanded form.

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?

The description is severely incomplete for a tool with four parameters, no output schema, and no parameter documentation. It does not explain what a 'graph wiki' is, what the tool returns, how to select parameters, or when it should be used. The complexity is low (read operation), but the description still fails to provide the minimum context an agent needs.

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 mentions only 'project metadata' without explaining any of the four parameters (nodeId, projectId, sessionId, executionId). The description provides no meaning for the required parameters, leaving the agent without guidance on what values to supply.

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 'Read hosted get graph wiki using privacy-filtered project metadata' uses a vague verb-resource combination. 'Graph wiki' is ambiguous and not defined, and the phrase closely mirrors the tool name without clarifying what the resource is or how it differs from siblings like get_graph_scope or get_context_graph. It does not distinguish this tool from other read operations.

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 on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions, and with many sibling read tools available, the agent receives no help in choosing this one.

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