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

Annotations already declare readOnly, idempotent, non-destructive behavior, so safety is covered. The description adds nothing beyond pointing to describe_operation for schemas; it does not say what 'effective' resolution means (inherited/overridden mappings) or what shape the response takes.

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 first sentence is duplicated verbatim and the rest is boilerplate metadata (operation ID). Nothing is front-loaded that helps an agent decide or invoke, so brevity here reflects emptiness rather than economy.

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 nested, undocumented query-object API with no output schema, an agent has essentially no information about what this returns or what to pass. The description is inadequate even for a simple read endpoint.

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 coverage is 0% and both parameters (a free-form 'query' object and an empty 'params' object) are opaque. The description offers no parameter meaning, only a redirect to describe_operation for request schemas, which is a weak substitute for actual semantics.

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 only restates the endpoint path 'GET /api/account-mappings/effective' twice, which is a tautology of the tool title/name. It never explains what 'effective' account mappings are or how that differs from the sibling get_account_mappings_5900b624a5f0d38407bcecf4 or get_account_mappings_by_id.

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?

No when-to-use guidance against the many account-mapping siblings. The only actionable hint is 'describe_operation provides native request schemas', which is a discovery pointer, not usage guidance.

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