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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds genuinely useful context beyond that: the data blends live store values with the draft flagged as current, and includes computed checks and keyword coverage. It says nothing about auth requirements, error behavior when the app is untracked, or payload size.

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?

It is a single sentence with no filler, but that sentence is a dense run-on noun phrase with nested parentheses that takes effort to parse. Front-loading the returned resource is good, yet the enumeration order and parenthetical clauses obscure the primary purpose.

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 output schema, the description must convey the return contents, and it does so item by item (listing, limits, checks, keyword coverage, drafts). The remaining gap is that 'checks on the live copy' is unspecified and there is no indication of result shape or whether missing data is omitted or null.

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?

Only one parameter (application_id) exists and schema description coverage is 100%, so the schema already carries the parameter burden. The description adds no semantics about the id (format, whether it is a store id or internal id, or what happens for an invalid id), so the baseline of 3 applies.

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 enumerates exactly what the tool returns for a tracked application: the live listing, store character limits, live-copy checks, keyword coverage, and saved drafts. That is a clear resource definition, but it is delivered as a noun phrase with no verb and never distinguishes it from near-siblings like check_listing_metadata, compare_metadata_draft, or get_application.

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?

There is no explicit when-to-use guidance and no mention of alternatives, even though the sibling list contains several overlapping metadata tools (check_listing_metadata, compare_metadata_draft, list_metadata_drafts). The agent must infer that this is the aggregate read for one application from the description's content alone.

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