parse_codebase_tool

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

With no annotations provided, the description carries full burden but only states a high-level action. It does not disclose whether parsing is recursive, permissions needed, effects on existing graph (overwrite vs merge), or error handling. This lack of behavioral detail limits agent understanding.

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 at the cost of missing critical details about parameters, usage, and behavior. It is under-specified, not efficiently conveying necessary information for an agent.

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 the tool's complexity (parsing a codebase into a graph) and lack of annotations, output schema, or param description, the description is far from complete. It omits language support, recursion, state interactions, and error behavior, making it insufficient for reliable agent use.

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?

The description does not explain the single parameter 'path' beyond implying it is a directory. With 0% schema description coverage, the description adds no value over the schema. It fails to specify format (absolute/relative), valid values, or constraints, leaving the agent without essential guidance.

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 clearly states a specific verb ('Parse'), resource ('code files in a directory'), and outcome ('into a knowledge graph'), distinguishing it from siblings like 'query_graph_tool' or 'reset_graph_tool'. However, it does not differentiate from 'parse_codebase_stream_tool' (streaming vs batch) but the core purpose is unambiguous.

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?

The description fails to provide any guidance on when to use this tool versus alternatives, such as 'parse_codebase_stream_tool'. No context about prerequisites, when not to use, or preferred scenarios is given, leaving the agent to infer usage.

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