Indique e Ganhe

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

Annotations already declare readOnlyHint and openWorldHint. The description adds critical behavioral context: strict scoping to the authenticated seller, exclusion of ranking and other sellers' data, and a detailed list of returned fields (total referrals, commissions by status, list, history). This goes beyond what annotations provide and helps the agent understand the exact nature of the tool.

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 sentence that efficiently conveys the tool's purpose, output fields, and constraints. It is front-loaded with key information and contains no redundant or unnecessary words.

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?

The tool has no inputs and no output schema, so the description must compensate. It fully covers the output by listing the major categories (total, commissions, list of referrers, history) and the scope constraints. This is sufficient for an agent to understand what the tool returns without needing an output schema.

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 no parameters, so schema coverage is 100%. The description does not need to add parameter information; the baseline score of 4 applies. The description does not mention any inputs, which is appropriate.

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 returns referral program statistics for the authenticated seller, listing specific data (totals, commissions breakdown, list of referrers, history). It also distinguishes itself from sibling tools by explicitly stating it is read-only and scoped only to the own seller, never returning ranking or other sellers' 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?

The description provides clear context: it is read-only and restricted to the own seller. It explicitly states what it does NOT do (never returns ranking or other sellers' data), which helps an agent avoid misuse. However, it does not name specific alternative tools for cases where other sellers' data or rankings are needed.

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