affiliate_connexity_list_clicks

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

Annotations are absent, so the description carries the burden. It discloses that it returns Click records and that clicks are 'recent', but does not state auth requirements, rate limits, or pagination behavior. The read-only nature is implied by 'list' but not explicitly declared.

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 purpose, followed by concrete use cases and a complementary tool. Every sentence earns its place with no redundancy.

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?

No annotations or output schema. The description provides purpose, use cases, and return type, but omits pagination semantics, parameter details, and any behavioral caveats. Adequate for simple use but not fully complete for autonomous invocation.

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 has 0% description coverage. The description mentions 'filtered by programme and date', which maps to programmeId and from/to, but does not explain limit, cursor, or offset. Partial compensation for the 0% coverage is insufficient for 6 parameters.

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 states 'List recent affiliate clicks on Connexity, optionally filtered by programme and date' – a specific verb, resource, and scope. It clearly distinguishes from sibling list_transactions by naming the traffic-side debugging purpose and specifying Connexity.

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 'Use this for traffic-side debugging' and gives example questions like 'are my links being clicked at all?'. It also directs to 'pair with list_transactions to compare clicks vs conversions', naming the complementary alternative.

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