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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower; the description's 'Read-only' merely echoes them. The genuine value-add is the domain behavior it discloses: that an ENABLED symbol causes TraderWAI to auto-execute suggested orders without manual review, which tells the agent the stakes of what it is reading.

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 the resource, followed by the meaning of the flag and the return shape. Three sentences with minimal waste; the inline return-shape object is justified because no output schema exists.

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?

With no input parameters, no output schema, and safety already covered by annotations, the description supplies the missing pieces: what the flag controls and the exact return fields (globalEnabled, configs with symbol/enabled/brokerConfigs/maxPerDay/skipIfOpenPosition). Adequate for a simple read tool.

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 tool takes zero parameters, which is the baseline-4 case. The description correctly adds no parameter detail because there is nothing to document, and instead documents the response shape.

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 (List) and resource (per-symbol auto-execution configuration plus global switch), and the sibling names set_auto_execution_config / delete_auto_execution_config make the read-only scope unambiguous. An agent can distinguish this from the setters and deleters without opening a 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?

The description explains what the returned configuration means and links it to suggest_order, which implies when an agent would care. However, it never states explicitly when to call this versus get_suggested_orders or the sibling set_/delete_ tools, and offers no exclusions.

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