get_classpath_info

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

Since no annotations exist, the description implies a read-only operation but does not explicitly state lack of side effects, permissions, or other behavioral traits beyond the dependency on load_project.

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 well-organized with USAGE, OUTPUT sections and a prerequisite note. It is mostly concise, though the first sentence and USAGE line partially repeat.

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 simple boolean parameters and no output schema, the description adequately explains output types and the dependency. It provides a clear understanding of what the tool returns.

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?

All three boolean parameters are fully described in the schema (100% coverage). The description mentions output types that correlate with parameters but adds no extra meaning beyond the schema.

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 explicitly states the tool retrieves project classpath information, lists output types (source folders, libraries, containers), and distinguishes from sibling tools like get_project_structure by focusing on classpath.

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 provides a prerequisite (load_project) and a usage statement, but does not explicitly guide when to use this tool over alternatives or state 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.