get_agent_network_stats

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Get ... statistics,' which is essentially a restatement of the tool's name. It does not explicitly state that it's read-only, what data it aggregates, or any potential side effects or rate limits.

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 a single, front-loaded sentence with no wasted words. However, it's almost too terse, lacking any elaboration on what 'statistics' includes. Still, for a no-parameter tool, this length is appropriate.

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?

There is no output schema, so the description should explain what the tool returns. It merely says 'statistics,' which is vague and fails to convey the specific metrics (e.g., total affiliates, commission volume) that an agent would need to interpret the result. This is a significant gap given the lack of structured output information.

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 input schema has zero parameters, so the baseline is 4 per rubric. The description adds minimal meaning with 'overall,' implying the statistics are aggregate and not filtered, which offers slight value beyond the empty 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 uses the verb 'Get' and specifies a unique resource: 'overall AI agent affiliate network statistics.' The word 'overall' hints at a network-wide scope, distinguishing it from sibling tools like get_my_affiliates or get_commission_info, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus the many affiliate-related siblings (e.g., get_affiliate_info, get_referrals). There are no exclusions, alternatives, or context that would help an agent choose this tool over others.

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