estimate_solder_joint_thermal_fatigue

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real behavioral context instead — the physics performed (CTE-mismatch shear strain over DNP, creep-aware exponent with hot dwell and mean joint temperature) and the reported metric (cycles to 63.2% failure versus required cycles). It stops short of noting assumptions or validity limits of the Engelmaier model, which would be the last step to a 5.

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?

A single dense sentence that front-loads the standards and the verb before the method details, with no filler. It is long but every clause (strain range, creep exponent, dwell/temperature, reported metric, profile range) carries 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?

With 11 optional parameters and no output schema, the description does the necessary work of saying what comes back (cycles-to-63.2%-failure against the service requirement), so an agent can interpret the result. Missing only method preconditions and how overrides interact, which the schema partly covers.

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 every one of the 11 parameters is already documented with defaults and units; baseline is therefore 3. The description reinforces the roles of DNP, hot dwell, and the TC1-TC4 conditions but adds no syntax, coupling, or edge-case guidance (e.g., how explicit temp_max_c/temp_min_c interact with condition) beyond what the schema states.

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?

States a specific verb-and-resource pair ('thermal cycling fatigue life estimator' for solder joints) and names the governing standards (IPC-9701A / IPC-D-279 Engelmaier). The domain is specific enough that an agent can separate it from siblings like predict_assembly_mtbf or assess_drop_shock_reliability, though it never names an alternative explicitly.

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?

Scope is implied by 'critical SMT attachments' and 'against the service requirement across TC1-TC4 automotive/aerospace profiles', so an agent can infer the fit. But there is no explicit when-to-use/when-not statement, no prerequisite guidance (e.g., needing DNP and CTE data first), and no routing to a sibling such as predict_assembly_mtbf.

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