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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still earns credit by disclosing what the surface contains — prioritized work, a recommended next step, and four growth areas — which is behavioral detail annotations cannot convey.

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?

Two sentences, front-loaded with the action and then the trigger condition. Nothing is redundant, though the content enumeration could have been compressed slightly to keep the routing guidance adjacent to the verb.

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 carries the burden of telling the agent what comes back, and it names the three headline sections it returns. It does not describe structure or ordering in detail, but for a zero-required-parameter read dashboard this is close to sufficient.

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?

There is a single parameter with 100% schema coverage, and the schema already explains the default behavior when store is omitted. The description's phrase "for a store" only echoes that; it adds no selection or format guidance beyond the schema, so 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?

The description gives a specific verb and resource ("Open Fudge Home") and enumerates the content the tool surfaces: pending merchant work, the next recommended step, and the four growth areas. That is more concrete than a restated title, though it never names a sibling such as get_store_overview or list_work to sharpen the boundary.

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?

"Use when the merchant asks to open Fudge or see their store at a glance" gives an explicit trigger tied to merchant intent, which is solid context. It stops short of exclusions — an agent cannot tell from this text whether a plain overview request should go here or to get_store_overview.

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