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

Goes beyond the annotations by explaining the actual semantics of the switch: OFF overrides per-symbol config entirely (kill-switch), ON defers to per-symbol configs. That is real behavioral context not encoded in destructiveHint/openWorldHint. It does not address idempotency or the effect on already-pending suggested orders, so it is not exhaustive.

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?

Three sentences, each earning its place, with the master-scope claim and the kill-switch consequence front-loaded before the usage guidance. No filler or restatement of the tool name.

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 one-parameter, no-output-schema toggle, the description covers scope, precedence over per-symbol config, and intended usage. The only gap is behavior toward in-flight or pending suggested orders when the switch flips off, which an agent might reasonably need to know.

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 100% and the single boolean parameter is fully documented in the schema itself, so the baseline is 3. The description reinforces the meaning of the flag by describing the downstream consequence (all symbols blocked vs. per-symbol rules apply), but adds no syntax or format detail beyond that.

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?

States a specific verb+resource ('Master on/off switch for ALL auto-execution') and immediately scopes it against per-symbol config, which is exactly the distinction needed versus sibling set_auto_execution_config. An agent can tell it apart from the per-symbol tool without opening either schema.

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 states the use case ('Use this to pause or resume all auto-execution at once without touching per-symbol settings'), which routes the agent away from per-symbol configuration. The alternative is described functionally rather than named as a sibling tool, so it stops just short of a 5.

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