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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description's only added behavioral value is naming the kind of content returned (offers, campaigns, bars, widgets and settings) — useful given there is no output schema — but it says nothing about depth, volume, or whether unpublished changes are excluded.

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 compact sentence with the scope front-loaded and no filler. It reads as a fragment ('What is live right now...') rather than stating the operation directly, which slightly weakens the opening for an agent scanning tool lists.

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 two-parameter read-only tool with no output schema, the definition tells the agent it returns live configuration for one app and that app selection is enum-constrained. The main remaining gap is routing guidance against the draft-oriented siblings (list_drafts, preview_draft), which the description never addresses.

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 spelling out every app and its features and the store parameter explaining the default-store fallback. The description adds nothing beyond that, which is acceptable given the schema does the work, but it earns no extra credit.

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 names a concrete verb-less but specific operation: reading the currently live configuration (offers, campaigns, bars, widgets, key settings) of a single app. That scope is clear enough to distinguish it from get_item/list_items, though it never explicitly names a sibling or says it is the live-vs-draft view, so differentiation is inferred rather than stated.

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?

'What is live right now' hints that this reflects published state rather than drafts, which is a weak implicit signal. There is no explicit when-to-use statement, no mention of when to prefer list_drafts/preview_draft/get_item instead, and no prerequisites such as store selection.

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