runClass

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

No annotations are provided, so the description carries full burden. It fails to disclose whether this is a read or write operation, what side effects occur, or what the return value is. The agent has no information about behavior.

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 extremely concise, but this is a case of under-specification, not efficient communication. While it is short, it fails to provide essential information, making it less useful.

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 no output schema, no annotations, and only 50% parameter coverage, the description is severely incomplete. For a tool with a required parameter and no behavioral context, the description provides almost no useful information for an agent to call it correctly.

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 50%—only the 'connection' parameter has a description. The required 'className' parameter is not described, and the description adds no meaning beyond the schema. The agent cannot infer the format or purpose of className.

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 'Runs a class.' is vague. It does not specify what 'run' means—executing a method, running as a program, or testing. The name 'runClass' suggests execution, but the verb 'runs' is generic and not differentiated from sibling tools like unitTestRun or checkRepo.

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 context signals list many sibling tools with overlapping domains, but the description provides no selection criteria or prerequisites.

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