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

With no annotations, the description must carry the full burden. It says 'Describe,' implying read-only, but doesn't explicitly state non-mutating behavior, authentication requirements, or what the return value looks like. It gives no detail on side effects, latency, or data freshness.

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?

The description is a single, tight sentence that names three distinct aspects. No filler words. It is perfectly concise and front-loaded with the subject matter.

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?

Given there is no output schema, no annotations, and no parameters, the description is the only source of guidance. It mentions three topics but doesn't specify the format, depth, or whether it returns a simple status flag or a detailed report. An agent cannot infer expected output or prerequisites, making it insufficiently complete.

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 are zero parameters, so the schema already covers everything (100% coverage). The description doesn't need to add parameter details, and it doesn't. Baseline 4 applies because there is nothing to explain.

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 clear resource ('agent spend controls, reputation and marketplace economics') and a verb ('Describe') that indicates a read/informational tool. It distinguishes itself from siblings like payment_status and settlement_status by covering a broader commerce-economics scope, though it doesn't specify the exact output form.

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?

No guidance is given on when to use this tool versus the many siblings (e.g., payment_status, settlement_status, provider_health). An agent has no clue whether this is the right tool for a specific commerce status need or when a sibling is more appropriate.

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