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

The readOnlyHint annotation already communicates that the operation is safe. The description adds only static content descriptors (balances, muse keys, budget) rather than behavioral details such as side effects, authentication requirements, rate limits, or how the information is returned. It does not contradict the annotation.

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 extremely brief, a single noun phrase with a colon-separated list. Every word contributes to defining the resource, there is no filler. It is arguably under-specified, but from a pure conciseness standpoint it is efficient.

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 one required parameter, no output schema, and no parameter documentation, the description is too thin. It tells the agent what an account is in the abstract but not how to call the tool meaningfully, what the response shape is, or what scenarios call for it. The readOnlyHint covers safety but not operational completeness.

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?

Schema description coverage is 0%, and the description does not mention the address parameter at all. An agent gets no guidance on what address means, its expected format, or how it relates to the account contents, leaving the schema's bare string type as the only information.

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 identifies the resource as a MetaMuse account and enumerates its contents: balances, registered muse keys, and budget left. It is clear enough to infer the tool retrieves an account summary, though it lacks an explicit verb like 'get' or 'fetch'. It does not explicitly distinguish itself from sibling tools like metamuse_assets, but the listed fields give it a distinct identity.

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 provides no guidance on when to use this tool versus alternatives such as metamuse_assets or metamuse_summary. There are no exclusions, prerequisites, or context cues about the appropriate invocation scenario.

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