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

With no annotations, the description carries the full burden for behavioral disclosure. The verb 'List' correctly implies a non-mutating read operation, and 'No harness data is accepted' clarifies an input constraint. However, it does not describe the return format or whether any authentication/rate limits apply, leaving some behavioral ambiguity.

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 only two sentences, front-loaded with the primary action and then a clarifying constraint. There is no fluff or redundant information; every word earns its place.

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 simple no-parameter tool, the description covers the key aspects: what is listed (products and payment modes) and an important constraint (no harness data). It does not explicitly state the return format, but the verb 'List' implies the output is a listing. Given the low complexity, this is nearly complete, though a tiny bit more detail about output would make it fully 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?

With zero parameters, the baseline is 4. The description adds the note 'No harness data is accepted,' which reinforces the absence of parameters and clarifies that no input is expected. This adds a small semantic touch beyond the empty 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 clearly states the tool's purpose with a specific verb ('List') and resource ('agent-readable Bring Your AI products and supported payment modes'). It distinguishes itself from siblings like list_targets by focusing on products rather than targets, and the qualifier 'agent-readable' adds useful scope.

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 implies a clear use case: when you need to see available products and payment modes. However, it does not explicitly mention when NOT to use it or name alternative tools like list_targets, so the guidance is implicit rather than explicit.

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