youfiliate_get_smart_link_stats

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds value by specifying non-modification and detailing the breakdown dimensions (country, device, referrer, day), as well as listing common errors.

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?

Description is concise and front-loaded, delivering key information in two sentences plus a brief error note. Every sentence adds value 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 output schema for return format, annotations for safety, and schema descriptions for parameters (though not in description), the tool is well-documented for a read-only stats retrieval. Includes error handling hints.

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 description coverage is 0% per context signals, meaning the description text must compensate. However, the description does not explain any parameters (id, period, response_format), leaving the agent to rely solely on the schema, which is insufficient for full understanding.

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?

Description clearly states it gets click analytics for a specific smart link, breaking down counts by country, device, referrer, and day. Title in annotations and verb+resource structure distinguish it from siblings like get_aggregate_stats.

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?

Provides clear context on what it returns and that it does not modify data. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions, such as when to use get_aggregate_stats instead.

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