calculate_light_year_distance

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

No annotations are provided, so the description must disclose behavioral traits. It only specifies the return format (light_years, parsecs, au, km, original) and does not mention idempotency, side effects, rate limits, or other behaviors. Given the tool is a read-only conversion, the description is minimally transparent.

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 concise with two sentences. The first sentence states the core purpose, and the second provides output structure and a pointer to related calculators. It is front-loaded and efficient, though the pointer to list_bundles could be considered extraneous.

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 low parameter complexity and the presence of an output schema (as indicated by context), the description adequately covers the conversion purpose and output fields. It lacks only a brief note on when to use this instead of other conversion tools, but overall it is sufficiently complete.

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 100% description coverage; both parameters (value and from_unit) are documented in the schema with types and enums. The description adds no extra semantic details beyond what the schema provides, so it meets the baseline but does not exceed it.

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 converts astronomical distances between four specific units (light-years, parsecs, AU, km). The verb 'convert' and resource 'astronomical distances' are specific, distinguishing it from siblings like calculate_light_year or convert_distance.

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 mentions 'See list_bundles for related 'astronomie-nature' calculators', which hints at related tools but does not provide explicit guidance on when to use this tool versus alternatives like calculate_light_year or convert_distance. Usage context is implied but not clearly defined.

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