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

Even though no annotations are provided, the description clearly conveys that this is a read-only informational call ('Show') and discloses an important authentication requirement (X-Mako-Key header from makometrics.com/portal). It does not detail error behavior or output format, but the behavior is simple and well-scoped.

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, each earning its place: what is shown, when to call it, and what credential is required. The most important information is front-loaded and there is no filler.

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, no-output-schema tool, the description covers everything needed to invoke it correctly: purpose, call ordering, and authentication. Nothing critical 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?

The tool has zero parameters, so the schema provides no meaningful burden and the description correctly adds none. The pointer to the required header is useful contextual information beyond the schema.

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 specific verb ('Show') and a specific resource (the Mako Metrics account tied to this key), and enumerates exactly what is revealed: plan, remaining competitor reports, and client workspaces. This clearly distinguishes it from all sibling tools like list_clients or create_order.

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 description explicitly says to 'Call this first in any session that will use the customer tools,' providing clear situational guidance. It does not mention when not to use it or offer alternatives, but none are needed given its unique role.

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