set_executor_mode

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

Despite no annotations, description discloses full behavioral impact: toggles narration, and crucially states it does not silence errors or safety confirmations.

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?

Front-loaded with key purpose, well-organized with paragraphs for different aspects, but somewhat verbose with repetitions; still very effective.

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?

For a simple boolean toggle, description covers default behavior, when to invoke, edge cases, and exceptions (errors/safety), leaving no gaps.

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?

With 0% schema coverage, description fully explains the single boolean parameter: True/False meanings and usage scenarios, going beyond just typing.

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?

Clearly states 'Turn executor mode (concise, no-narration responses) on or off.' Identifies the specific verb and resource, and distinguishes from sibling get_executor_mode.

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?

Explicitly says call only when user asks to change response style, provides concrete examples for True/False, and notes it's unnecessary at conversation start.

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