set_angle_mode

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

Annotations already provide idempotentHint (true) and destructiveHint (false). The description adds valuable behavior: global mode can be overridden by per-call unit parameters. This clarifies the interaction between global and local settings, which annotations alone do not convey.

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?

Two sentences with no wasted words. The first sentence states the core purpose, and the second adds essential context about override behavior. Perfectly front-loaded and concise.

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 description is adequate for a simple tool with one parameter and no output schema. However, it could be more complete by explicitly linking the global mode to subsequent trig function calls or explaining the absence of a return value. The minimal information leaves some gaps for the agent.

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?

Schema description coverage is 0%, requiring the description to clarify parameters. However, the description only mentions 'unit param' without mapping to the actual 'mode' parameter. It does not explain the meaning of the enum values ('degrees', 'radians') 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's action: 'Set global trig angle mode.' It distinguishes from the sibling 'get_angle_mode' and explicitly mentions the override behavior with per-call unit parameters, making the purpose precise and differentiating it from individual call settings.

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 when to use this tool (for global setting) but does not explicitly contrast it with alternatives like 'get_angle_mode' or when to prefer per-call overrides. No when-not-to-use guidance is provided.

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