calculate_light_year

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

No annotations are provided, so the description must carry the full behavioral disclosure. It states 'Convert' implying a non-destructive read operation, but it does not describe any side effects, required permissions, or limitations. The conversion factor is given but not how the conversion is performed (e.g., if it handles large 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 short but contains both useful information (conversion factor) and misleading information (parameter list). It is not well-structured with front-loaded critical info; the parameter list is confusing. Every sentence does not earn its place due to inaccuracies.

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 input schema has only two parameters and an output schema exists, the description fails to explain how to use the unit parameter correctly (e.g., that it specifies the input unit and the conversion is to other units). It does not cover edge cases or error handling. The inaccuracy with parameters adds to incompleteness.

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 description claims 'Inputs: value, from, to' but the input schema only has 'value' and 'unit', with no 'from' or 'to' parameters. This misrepresentation confuses the agent about the actual parameters. Although schema coverage is 100%, the description actively adds incorrect information rather than adding value.

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 states 'Convert between light-years and km/miles' and 'Use for astronomy', which gives a general purpose. However, it is inaccurate because the input schema includes parsec, au, and km but not miles. Additionally, the sibling tool 'calculate_light_year_distance' exists but no differentiation is provided. Clarity is reduced by the mismatch between description and schema.

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 minimal usage guidance: 'Use for astronomy.' No explicit when-to-use or when-not-to-use, and no mention of alternatives. It references list_bundles for related calculators but does not differentiate from the sibling 'calculate_light_year_distance' tool.

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