setMmp

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

The description discloses that the tool configures MMP, requires all parameters, and specifies that frozenPeriod can be '0' for permanent freeze. It also mentions rate limits and decimal constraints. However, it does not describe side effects, authorization needs, idempotency, or what happens upon invalid input.

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 reasonably concise, with the purpose stated upfront. The agent hint repeats some information, but it's still succinct and well-organized.

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?

The description covers the purpose and parameter details well, but given no annotations and no output schema, it lacks information about the return value, error conditions, and overall effect. It is adequate for a simple configuration tool but could be more complete.

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, the description adds crucial meaning: it specifies that 'window' and 'frozenPeriod' are in milliseconds, and that 'qtyLimit' and 'deltaLimit' are positive numbers with max 2 decimals. This goes well beyond the schema's raw string type.

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 clearly states the verb 'Configure' and the resource 'Market Maker Protection parameters for options trading'. It distinguishes itself from the sibling tool 'resetMmp' by mentioning the configuration purpose and the reset endpoint.

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 states that all parameters are required and gives a hint about frozenPeriod and the rate limit. However, it does not explicitly specify when to use this tool versus other configuration tools or alternatives, and lacks guidance on prerequisites or scenarios where it should not be used.

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