context.mode_set

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

With no annotations, the description carries the full burden. It discloses the primary behavior (switching mode) and the optional activation, but does not elaborate on side effects, undo behavior, or what happens if the object is not found.

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 a single, well-structured sentence that conveys the essential information. It is concise without being overly terse, though it could slightly expand on parameter behavior.

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 simple action and no output schema, the description provides a baseline understanding. However, it lacks details on error conditions or the impact on the current scene, making it adequate but not thorough.

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 coverage is 0%, so the description must add meaning. It explains the 'object' parameter implicitly via 'optionally activating an object first' and 'select' is partially inferred, but the 'select' parameter (default true) is not explicitly mentioned. Only 2 of 3 parameters get partial explanation.

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 explicitly states the action (Switch) and the resource (Blender interaction mode), and notes the optional object activation. This is specific and distinguishes this tool from other context tools like context.select_objects.

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 usage for changing modes but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites beyond optional activation.

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