calculate_angle_convert

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

No annotations provided, but the tool is a straightforward unit conversion with no side effects. The description does not add behavioral details beyond the basic operation, which is acceptable for such a non-destructive tool.

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 concise: two short sentences directly communicating the purpose, units, return format, and a hint to related tools. Every word earns its place.

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 simplicity of the tool and the presence of an output schema, the description adequately covers the conversion intent and units. The placeholder return format is minor; overall, it provides sufficient context for a basic converter.

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 provides full descriptions for all three parameters (100% coverage), so the description adds minimal additional meaning. It confirms allowed units but doesn't elaborate beyond the schema.

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 angles among degrees, radians, gradians, and turns, matching the verb and resource. The placeholder '{original}' in the return format is slightly ambiguous, but doesn't detract from understanding the primary purpose.

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 indirectly points to related tools via list_bundles, but does not explicitly state when to use this converter over sibling convert_* tools. A clearer directive would improve selection.

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