affiliate_scaleo_get_programme

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

No annotations are provided, so the description must carry the burden. It states that it returns a single Programme and hints at read-only via 'Fetch', but does not explicitly mention error behavior, auth requirements, or confirm that no side effects occur. This is adequate but not fully comprehensive.

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 efficient sentences with no fluff. The action is front-loaded, usage guidance follows, and the alternative is clearly named. 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 single-parameter fetch tool, the description covers purpose, usage, return type, and key fields. No output schema exists, so the description adequately explains the return value. The pairing with list_programmes completes the workflow context.

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% and there is no param description, but the description compensates by explaining the parameter is the network programme id and when you need it. It adds semantic meaning beyond the bare schema.

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 Scaleo by network programme id, listing specific fields returned (commission, status, advertiser URL). This distinguishes it from sibling list_programmes and other get_programme tools across networks.

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 says to use when you already know the programme id and need the full record, and pairs with list_programmes for id discovery. This gives clear when-to-use and alternative guidance.

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