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

The description states 'Read-only', consistent with annotations. It adds that a connected account is required, which is behavioral context beyond annotations.

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 with no fluff. Every word adds value, efficiently conveying purpose, output, filter, and requirements.

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 list tool with one optional parameter and no output schema, the description covers the essential aspects. Could mention pagination or sorting but not necessary for basic understanding.

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 only parameter (tier) is mentioned as 'Optional tier filter', but no details on valid values or format are given. Schema coverage is 0%, so description partially compensates but remains minimal.

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 lists sponsors and specifies the output fields (company, tier, total committed, deliverables, contact, grand total). It distinguishes from sibling tools like list_affiliates or list_deals by focusing on sponsor-specific data.

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?

It states an optional tier filter and requires a connected account, providing clear context for when to use. However, it does not explicitly compare to alternative tools or state when not to use.

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