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

No annotations are provided, so the description carries the full burden. It discloses the free tier limit (500 calls/day), the not-metered behavior, and the upgrade cost/URL, which are useful non-obvious traits. But it doesn't state whether this is a read-only operation, what 'key or IP' scoping means for auth, or the response shape.

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-loads '[run-memory]' namespace and the core action, packs free tier and upgrade info efficiently. A single sentence but dense; no wasted words.

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 zero-param informational tool with no output schema, the description covers the key facts (usage, upgrade link, pricing). It doesn't explain return format or what 'today's usage' includes, which would help an agent know whether to call it. Adequate but minimal.

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?

Zero parameters, so the baseline is 4. The description correctly implies no inputs are needed and identifies the implicit scoping (key or IP).

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 (Show) and resource (today's usage for key or IP) plus the upgrade link. The 'usage_and_upgrade' pattern is a sibling family tool, and the description clearly identifies what this instance covers (memory/run-memory) versus budget/loop/approve/wake variants.

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 'Not metered' and free tier limit provide clear context on when this is useful. However, it doesn't explicitly say when to use this versus memory_weekly_report or memory_list_checkpoints, or that no parameters are needed to get the key's usage.

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