calculate_cable_section_electrical

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

No annotations are provided, so the description must carry the full burden. It states the tool is a pure calculation that returns a structured result. This is adequate for a simple calculator with no side effects or destructive actions. However, it omits details on performance, accuracy, or constraints beyond input schema.

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 with two sentences. The first sentence clearly states the purpose, and the second lists the return structure and a pointer to related tools. No unnecessary words or details.

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?

The description covers the tool's purpose, input parameters (implicitly via text), and output structure. However, given the complexity (4 params, 2 required), it could provide a usage example or clarify units (though schema descriptions cover that). It is sufficient for a straightforward calculator.

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 coverage is 100% with all parameters described. The description lists the same parameters but does not add meaningful new information beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting, and the description does not enhance understanding of parameter behavior.

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 'Calculate cable section from power, voltage, distance and max voltage drop' which specifies the verb and resource. However, it does not differentiate from sibling 'calculate_cable_section' or other related calculators, nor does it clarify the return structure in a unique way.

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 no guidance on when to use this tool versus alternatives. The only reference is 'See list_bundles for related science calculators', which is vague and does not specify conditions or exclusions. No explicit 'when-to-use' or 'when-not-to-use' is given.

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