affiliate_netrefer_verify_auth

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

With no annotations, the description carries the full burden. It discloses the call to a 'minimal authenticated endpoint', the return shape '{ok:true, identity?} or {ok:false, reason}', and its role as a lightweight auth check. This gives the agent insight into what to expect and how to interpret results.

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?

The description is three sentences, front-loaded with the main action, and every sentence adds value. It covers purpose, usage, and return details without 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?

Given the simplicity of a zero-parameter tool, the description is fully complete. It explains the return values, when to use it, and how it relates to a broader diagnostic tool, leaving no ambiguity for an agent.

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?

The tool has zero parameters and an empty schema, so the baseline is 4. The description appropriately avoids discussing parameters since there are none, and it adds value by explaining the return structure and use cases.

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's purpose: 'Verify the configured credentials for NetRefer are valid by calling a minimal authenticated endpoint.' This identifies the specific network (NetRefer), the action (verify auth), and the mechanism (minimal endpoint), distinguishing it from sibling verify_auth tools for other 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?

Explicit usage guidance is provided: 'Use this at the start of a session, after rotating keys, or when another operation returns an auth error.' It also directs users to 'affiliate_run_diagnostic' for a full health check, effectively ruling out this tool for deeper diagnostics.

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