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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds no behavioral context beyond that. It doesn't confirm read-only behavior, explain side effects, mention authentication needs, or clarify the nature of the external interaction.

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, short sentence with a clear front-loaded topic ('Who places the order...') and a list of modes. It is not verbose, though its phrasing as a question rather than an action statement slightly undermines clarity.

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 tool with no parameters and only read-only/open-world annotations, the description still fails to state the operation being performed. An agent cannot determine whether invoking it retrieves the current gating mode, sets a policy, or does something else entirely.

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 has zero parameters, so there are no parameter semantics to describe. The baseline for a parameterless tool is 4, and the description neither adds nor detracts from parameter understanding.

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 names the domain (broker MCP servers and order placement) and lists possible gating modes, but it never states what the tool actually does. It does not specify whether it reads, sets, or otherwise manipulates the gating policy, leaving the core verb absent.

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?

There is no guidance on when to use this tool, what prerequisites exist, or how it relates to alternatives such as compare_tools or get_tool. The description only presents possible order-placement modes without indicating when an agent should invoke the tool.

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