affiliate_kwanko_get_programme

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

No annotations exist, so the description carries the full burden. It conveys a read-only fetch via the verb 'Fetch' and names returned fields, but it does not explicitly state safety characteristics, authentication prerequisites, or error/not-found behavior. The behavioral disclosure is adequate but not rich.

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 concise sentences, front-loaded with the core action, followed by usage guidance and return details. No filler or redundancy; every sentence 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 one-param, no-output-schema tool, the description covers purpose, input semantics, return content, and the discovery workflow via list_programmes. It omits error/not-found handling and explicit auth notes, but those are not critical for a low-complexity fetch.

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%, but the description compensates by explaining that programmeId is the network programme id and indicates when you'd already have it (or need list_programmes to discover it). This adds meaningful semantics beyond the bare string type, though it doesn't specify format constraints.

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 it fetches a single programme by its network programme id on Kwanko, with a specific verb and resource. It explicitly distinguishes itself from list_programmes, making its purpose unambiguous among the many sibling 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?

The description provides explicit when-to-use guidance by stating 'Use this when you already know the programme id' and contrasts it with list_programmes for id discovery. This gives direct situational context and an explicit alternative, meeting the highest bar.

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