ln10

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 discloses the tool returns a constant value (ln(10) ≈ 2.30259), which implies it's a read-only, deterministic operation with no side effects. However, it doesn't explicitly state behavioral traits like whether it requires inputs, error conditions, or performance characteristics. The description adds basic context but lacks depth for a tool with zero parameters.

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 front-loaded: it states the core purpose in the first phrase ('Get ln(10) ≈ 2.30259'), adds explanatory context ('Natural logarithm of 10, conversion factor for logarithms'), and includes domain/category tags efficiently. Every sentence earns its place with no wasted words.

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 (zero parameters, no annotations, no output schema), the description is reasonably complete. It explains what the tool returns and its mathematical significance. However, it could be more explicit about the tool's behavior (e.g., that it always returns the same constant) and usage compared to siblings. For a basic constant-fetching tool, this is adequate but not exhaustive.

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 with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, and it appropriately doesn't mention any. It focuses on the constant output, which is sufficient given the parameterless nature. Baseline is 4 for zero parameters as per guidelines.

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 the tool's purpose: 'Get ln(10) ≈ 2.30259. Natural logarithm of 10, conversion factor for logarithms.' It specifies the exact mathematical constant returned and its application context. However, it doesn't explicitly differentiate from sibling tools like 'ln' (which computes natural logarithms generally) or 'log10' (which computes base-10 logarithms), though the constant nature is implied.

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 with 'conversion factor for logarithms' and domain/category tags, suggesting it's for arithmetic/general calculations. However, it lacks explicit guidance on when to use this specific constant tool versus computing ln(10) dynamically with the 'ln' tool or using other logarithm-related tools. No alternatives or exclusions are mentioned.

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