ln2

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

No annotations are provided, so the description carries the full burden. It describes the tool as a simple retrieval ('Get') of a constant value, which implies it is a read-only, non-destructive operation with no side effects. However, it does not disclose potential behavioral traits like error handling, performance, or output format details. The description adds basic context but lacks depth for a tool with zero parameters and no output 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 highly concise and well-structured: a single sentence front-loaded with the core purpose ('Get ln(2) ≈ 0.69315'), followed by clarifying context. Every word earns its place, with no wasted information, making it easy for an AI agent to quickly understand the tool's function.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is reasonably complete. It explains what the tool returns (ln(2) ≈ 0.69315) and provides domain context. However, it could be more complete by explicitly stating the output type or format, especially since there is no output schema. The description covers the essential aspects but has a minor gap in output specification.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and context. This meets the baseline for tools with no parameters, as it avoids unnecessary repetition and adds value through domain information.

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 explicitly states the tool's purpose: 'Get ln(2) ≈ 0.69315. Natural logarithm of 2, appears in information theory.' It provides a specific verb ('Get'), the exact resource (ln(2)), and distinguishes it from siblings by focusing on this specific constant rather than general logarithmic calculations. The additional context about its appearance in information theory further clarifies its domain relevance.

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 implies usage context through the phrase 'appears in information theory' and categorizes it under 'arithmetic, general,' which helps identify when this constant might be needed. However, it does not explicitly state when to use this tool versus alternatives like the general 'ln' tool or other constant tools (e.g., 'e', 'pi'), nor does it provide exclusions or prerequisites. The guidance is clear but lacks explicit sibling differentiation.

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