Cable Cross-Section & Resistance Calculator

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

Discloses key behavioral traits: considers ampacity and voltage drop, returns resistance, power loss, and fuse recommendation. No annotations provided, so description carries the burden and does so adequately, though a note that it is read-only could be implied.

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?

Three sentences, no wasted words. First sentence captures the primary purpose, subsequent sentences add key details without extraneous information.

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?

No output schema, but the description lists what the tool returns (recommended gauge, resistance, power loss, fuse recommendation). It also states the conductor range. This is sufficient for a utility tool, though a bit more detail on the output format could help.

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 100%, so baseline is 3. The description adds value by explaining that it supports copper conductors from 0.75 mm² to 240 mm² and mentions the dual input of current or power, which enhances understanding 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?

Clearly states the tool calculates recommended wire gauge/cable cross-section for DC circuits, specifying the resource and verb. Differentiates from sibling tools that focus on batteries, solar, inverters, etc.

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?

Describes the context for usage (DC circuits, ampacity and voltage drop considerations). No explicit exclusion or alternative guidance, but the context is clear enough for an AI agent to infer appropriate use cases.

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