affiliate_flipkart_get_programme

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

With no annotations provided, the description discloses the return type ('Returns a single Programme') and key fields (commission, status, advertiser URL). It does not mention auth or error behavior, but for a fetch operation this is a minor gap, not a contradiction.

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 sentences, front-loaded with the core verb and resource. Every sentence adds value: what it does, when to use it, and its output. No redundant or filler content.

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 1-parameter fetch tool, the description covers purpose, usage, return content, and relationship to sibling tools. It lacks error-case details or authentication prerequisites, but the simplicity reduces the need. Overall adequate for an agent to invoke correctly.

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?

Schema coverage is 0%, so the description is the only source for parameter meaning. It explains that programmeId is the 'network programme id' and clarifies how to obtain it ('discover via list_programmes'). This adds meaningful context beyond the bare schema, though an example or format would push it higher.

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 fetches a single programme on Flipkart Affiliate by network programme id. It distinguishes itself from list_programmes by emphasizing 'single' and 'by its network programme id', making it unambiguous.

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?

Explicitly states when to use: 'when you already know the programme id and need its full record.' It also names the alternative: 'pair with list_programmes when you need to discover the id first.' This is clear guidance.

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