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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing: no mention of return value, units, precision, or side effects. An agent has no idea whether invoking this tool returns a number, a string, or performs any observable action.

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 short but not meaningfully concise; it redundantly repeats the tool name in a heading-like format. Every word is wasted, and there is no substantive content. This is under-specification rather than efficient brevity.

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 no output schema and no annotations, the description is the sole source of information, yet it says nothing about what the tool returns. Even for a simple parameterless constant lookup, an agent must be told that it returns the elementary charge value, and ideally its units. The description is entirely inadequate for correct invocation or interpretation of results.

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 tool has zero parameters and the input schema is an empty object, so there are no parameter semantics for the description to clarify. The baseline of 4 for parameterless tools applies here because no parameter documentation is needed.

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 is a pure tautology: "Elementary Charge: Elementary Charge" simply restates the tool name twice. It contains no verb or action, so an agent cannot tell whether this tool returns the constant value, converts units, or performs some calculation. It identifies a physics concept but fails to state what the tool does with it.

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?

There is no guidance on when to use this tool versus alternatives. Among a vast sibling list containing other physical constants like avogadro, boltzmann, and earth-gravity, nothing distinguishes this tool or indicates the appropriate context. The description neither names alternatives nor implies a selection criterion.

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