getMmpState

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

Annotations already mark the tool read-only; the description adds a rate limit, clarifies it returns both configuration and live freeze state, and explains key response fields. No contradiction with annotations.

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 well-organized with a purpose line, rate limit, agent hint, and field list. The agent hint partly repeats the first sentence and the required-parameter note duplicates the schema, but overall it is compact and scannable.

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 one required parameter and no output schema, the description covers the needed invocation details: what it does, how to call it, rate limit, and the key returned fields. It lacks exact baseCoin value conventions but not enough to prevent correct use.

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 description tells the agent that baseCoin is required and identifies it as the coin whose MMP settings are queried. However, it provides no format, examples, or allowed values, and with 0% schema coverage this is only the bare minimum.

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 uses a specific verb ('Query') and names the exact resource ('Market Maker Protection configuration and freeze status') plus the base-coin scope. It clearly distinguishes from mutating siblings like setMmp and resetMmp.

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 agent hint explicitly says to use this tool for checking MMP settings and freeze status. It does not name alternative tools or state when not to use it, but the read-only query framing and sibling set/reset tools provide clear context.

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