get_loads

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

No annotations are provided, so the description carries full burden. It mentions 'limit/truncated capping', indicating some behavioral trait, but does not disclose whether the tool is read-only, requires specific permissions, or has side effects. The behavior is only partially addressed.

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 short (two sentences) but at the cost of clarity. It is cryptic and uses unclear phrasing, making it not concise in an informative sense. Every sentence should earn its place, but here the first sentence is confusing.

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 has 2 parameters, no output schema, and moderate complexity (netlist terms), the description is severely incomplete. It does not explain return value, expected inputs, or how the tool integrates with siblings. The agent lacks sufficient context to use the tool 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 0%, so the description must explain parameters. It only mentions 'limit/`truncated` capping' but does not describe the 'path' parameter or provide syntax/format details. The description fails to add meaning beyond the schema for either parameter.

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 uses domain-specific jargon ('equipotential', 'leaf readers') without defining the action clearly. It vaguely states what the tool returns but does not explicitly state the verb or resource. The reference to 'Mirror of get_drivers' provides some context, but the purpose remains unclear for an AI agent.

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 mentions 'Mirror of get_drivers' as a sibling, hinting at similarity, but provides no explicit guidance on when to use this tool versus alternatives. No usage conditions or exclusions are stated.

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