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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value by disclosing what the call returns ('with ids and status') in the absence of an output schema, though it says nothing about pagination, result ordering, or volume.

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?

A single sentence that front-loads the verb and resource, gives concrete item examples, and ends with the return payload. No filler, no repetition of the title.

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 three-parameter, fully documented read tool with rich annotations, the description covers purpose and return shape adequately. Minor gaps remain around result volume/pagination and cross-store listing semantics, but nothing an agent needs in order to invoke it correctly is missing.

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 100%, with the app enum exhaustively documented and store defaulting behaviour explained inline. The description adds nothing about the optional 'kind' parameter or the store fallback, so the schema does all the semantic work and baseline 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?

States a specific verb and resource ('List the editable items of an app') and enumerates concrete item examples (bundle offers, popup campaigns, bars), so an agent knows exactly what entity class comes back. It doesn't explicitly contrast with get_item or list_drafts, so sibling differentiation relies on the reader inferring 'list all vs. fetch one'.

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?

Usage is only implied: reach for this when you need the ids of an app's editable items. There is no explicit when-not guidance, no mention of get_item for single-item retrieval or list_drafts for uncommitted work, and the store-scoping advice lives in the schema rather than the description.

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