Graph

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

Annotations indicate not read-only or destructive, but the description adds little behavioral detail. It implies the tool modifies state (build, update) but doesn't disclose side effects or prerequisites.

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?

Description is dense but somewhat verbose. It lists actions and parameters inline, which is functional but not optimally structured. Could be more front-loaded.

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 9 parameters and only 1 required, and no schema descriptions, the description is insufficient. It covers action-to-parameter mapping but fails to explain parameter semantics and behavior. Output schema existence may help but is not referenced.

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 has 0% coverage, so description must compensate. It connects actions to parameters (e.g., build requires full_rebuild, base, repo_root), adding meaning beyond bare names. However, still omits explanation for several parameters like roots and format.

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?

Description clearly states the tool builds and manages a code knowledge graph, and lists specific actions. This distinguishes it from sibling tools like query or review.

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 on when to use this tool vs alternatives. The description lists actions but does not provide context for selecting between them or other tools.

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