NE555 Timer Calculator

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

The description details the mathematical formulas used (e.g., f=1/(0.693·(Ra+2Rb)·C)) and the output structure for both modes. Annotations already indicate idempotent, readOnly, non-destructive behavior, so the description adds transparency about the calculations and return values.

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 very concise, using just three sentences plus an example. It front-loads the purpose and formulas, then details args and returns, and ends with an illustrative example. No unnecessary text, every sentence adds value.

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?

Despite the tool's simplicity, the description covers the full scope: formulas for both modes, parameter descriptions, return value structure, and an example. With 100% schema coverage, an existing output schema (implied by the description), and clear annotations, the description is complete and leaves no ambiguity.

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?

The input schema already describes each parameter (e.g., 'Ra in ohms', 'Rb in ohms (astable only)'). The description reinforces this and adds context: it explains that rb_ohm is optional for monostable, gives units like 'e.g. 10e-6' for c_farad, and provides a concrete example. This 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?

The description clearly identifies the tool as an NE555 timer calculator. It specifies astable and monostable modes with formulas. The sibling tools include other embedcalc calculators, but this one is distinctly for NE555 timing, making selection unambiguous.

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 example usage and parameter requirements but does not explicitly state when to use this tool versus alternatives. However, the context of sibling names and the specific IC mention make the intended use obvious. A more explicit guideline could improve clarity.

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