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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds genuinely new context: no authentication needed and no store is read. What is missing is mention of pagination or whether the result is ever truncated, though the fixed count of 10 largely settles that.

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?

Three short sentences: contents first, then the auth guarantee, then the sibling disambiguation. Every sentence carries a distinct decision-relevant fact with no restatement of the title or annotations.

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 zero-parameter, read-only catalog lookup with no output schema, the description supplies exactly the missing pieces: what each entry contains, that auth is unnecessary, and how it differs from list_apps. Nothing an agent needs before calling is absent.

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 description correctly signals that no scoping input (store, auth token) is expected.

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?

"All 10 EA Shopify apps, what each one does, and a Shopify App Store install link for each" names the specific verb (list), the exact resource (EA apps), the fixed scope (10), and the per-item payload. It also explicitly separates itself from the sibling list_apps, so an agent can choose without inspecting either 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?

It states the selection rule outright: use this for the EA catalog, and use list_apps instead when the apps installed on the connected store are wanted. It also removes a common blocker up front by noting it works without signing in, so the agent knows no auth-gated path is required.

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