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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so "Read-only; changes nothing" largely restates structured data. The genuinely additive disclosure is that monetary values are integer minor units (cents), a data-shape trait not captured by any annotation.

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, front-loaded sentences with no filler. Minor deduction because "Read-only; changes nothing" duplicates the readOnlyHint annotation and spends a sentence on information already present in structured fields.

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 tool with no output schema, the description plus schema note convey the entry-point role, the kind of content returned (counts, currency, pending items, suggested actions), and the money format. Return structure remains only loosely sketched ("what is waiting" is vague), but the safety profile is fully covered by annotations.

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 the baseline is 4. The description still adds a useful unit convention (integer cents) that governs how the returned money fields should be interpreted, which is more than most no-param tools offer.

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?

"How the shop stands" is evocative but not a specific verb+resource; the real substance comes from the schema description ("Counts, currency, what is waiting, and what the shop's own state says needs doing"). Combined, an agent can infer this is a shop status/dashboard read, but the description alone does not clearly distinguish it from siblings like changes_status, sales_report, or promotions_state.

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?

The schema description gives a strong, explicit sequencing cue — "Call this first" — which is exactly the kind of when-to-use guidance this tool needs as the entry point. It stops short of naming alternatives or exclusions (e.g., when to prefer sales_report or changes_status instead), so it is clear context without full routing.

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