convert_angle

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

No annotations are present, and the description does not disclose behavioral traits such as side effects, read-only nature, or rate limits. It vaguely states 'Returns: {input}' which is uninformative and potentially misleading about the output.

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 and includes a cross-reference to related tools. However, it contains redundant information (listing inputs already shown in schema) and a vague return statement that could be omitted or clarified.

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?

The tool is simple, but the description misses clarifying the output format and introduces inconsistency with unsupported units. Given the output schema exists, the description need not detail output, but the inconsistency reduces completeness.

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 already provides full descriptions for all 3 parameters. The description adds minimal value beyond listing parameter names and some extra units not in schema, but this also introduces inconsistency.

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 between specified units and lists example units and use cases. However, it mentions arcminutes and arcseconds which are not in the input schema enum, causing potential confusion.

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 context for when to use (math, navigation, surveying) but does not explicitly differentiate from sibling tools like calculate_angle_convert or other conversion tools. The reference to list_bundles is helpful but not specific.

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