affiliate_adcell_get_programme

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

With no annotations, the description carries the burden of conveying behavior. 'Fetch' clearly indicates a read-only operation, and 'Returns a single Programme' describes the output. It adds context about the fields returned, but does not mention potential errors, authentication requirements, or rate limits, though these are less critical for a simple fetch-by-id.

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 filler: the first states the action and target, the second provides usage context and return info. Excellent front-loading and efficient use of 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?

For a simple tool with one parameter and no output schema, the description covers the key aspects: what it does, when to use it, what it returns, and how to discover the input. Missing details like error handling or auth are not critical for this simple fetch, making it fairly 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?

Schema coverage is 0%, so the description must compensate. It clarifies that programmeId is the 'network programme id' and explains the caller should already know it, hinting it comes from list_programmes. This adds meaning beyond the raw schema, though it lacks format specifics or an example.

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 Adcell programme by its network programme id, naming the network and resource. It also distinguishes from siblings by specifying the data fields returned (commission, status, advertiser URL) and pairing with list_programmes, avoiding confusion with other networks' get_programme tools.

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 explicitly states when to use the tool ('when you already know the programme id and need its full record') and provides an alternative ('pair with list_programmes when you need to discover the id first'). This gives clear when-to-use vs. when-not-to-use guidance.

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