getMmpState

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

The description lists key return fields (e.g., mmpEnabled, window, frozenPeriod) and explicitly states the rate limit (5 req/s), adding value beyond the input schema. It implies read-only behavior but does not explicitly confirm idempotency.

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 efficient with five sentences, front-loads the purpose, and includes a rate limit and agent hint without fluff. Every sentence adds value.

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?

Given the tool's simplicity (single parameter, no output schema), the description covers purpose, key return fields, and usage hint. It helps an agent understand the response structure, but lacks explicit read-only confirmation and parameter details.

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 only states that baseCoin is required, which duplicates schema information. With 0% schema coverage, it fails to explain the parameter's meaning (e.g., currency code like BTC) or expected format.

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 tool queries 'Market Maker Protection configuration and freeze status' for a specified base coin, distinguishing it from sibling tools like setMmp or resetMmp which handle mutation.

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 includes an agent hint to 'check MMP settings and freeze status,' implying a read-only usage intent, but lacks explicit guidance on when to use this tool versus alternatives (e.g., setMmp for modification).

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