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

Annotations already cover read-only, idempotent and safe semantics, and the description adds genuinely useful context beyond them: quota figures are 'as stored at readAt' rather than live, and it exposes the backing endpoint GET /accounts. It stops short of noting pagination or rate limits, which for a list endpoint would be the remaining gap.

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-loaded with the action and returned fields, then a one-clause disambiguation, then the endpoint. No filler sentences; the dense field list is informative rather than padding.

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 no input params and no output schema, the description must carry the return-value burden, and it does so by enumerating the salient per-account fields. It does not describe the overall response shape (e.g. list vs map, or account identifiers), a minor remaining gap for a schema-less list tool.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The text also confirms the only implicit input, the API token scope, is what determines the result set.

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 and resource (list the Muse accounts for this API token) and enumerates the per-account fields returned (health, maxJobs, session expiry, weekly usage/top-up with readAt). It explicitly contrasts with muse_get_account, so an agent can distinguish it from the sibling without opening the schema.

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?

Names the alternative tool and the condition that selects it: muse_get_account reads one account live, whereas this returns the stored snapshot for all accounts. The choice between the two is unambiguous.

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