graphify_explain

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

Annotations already indicate readOnlyHint=true, so the tool is safe. The description adds 'Return everything Graphify knows', which implies it may be expensive or broad, but no further behavioral traits are disclosed (e.g., what 'everything' includes). Given the annotation covers safety, a score of 3 is appropriate.

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, which is concise but lacks structure. It front-loads the purpose but omits details that would be helpful. It could be improved by adding a brief note on the parameter and perhaps a usage hint.

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 that an output schema exists, the description does not need to explain return values. However, with multiple sibling tools and a vague 'everything' claim, the description is minimally complete. It tells the agent what the tool does but not enough to differentiate or set expectations fully.

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 coverage is 0%, meaning the parameter 'node' has no description in the schema. The description does not explain what the parameter expects (e.g., node name, ID, format). It only implies it refers to a node. This is insufficient for an agent to correctly invoke the tool.

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 'Return everything Graphify knows about a node' clearly states the action (return) and the resource (everything about a node). It distinguishes from sibling tools like graphify_node_details or graphify_neighbors, which imply more focused queries, but does not explicitly differentiate. The purpose is clear but could be more specific.

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 usage guidelines are provided. The description does not specify when to use this tool versus other similar tools such as graphify_node_details or graphify_search. There is no guidance on prerequisites, limitations, or when not to use it.

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