get_manual_tracking_links

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Generate', implying a non-mutating creation of links, but does not clarify side effects, whether anything is stored, return format, or what 'manual' means in practice. This is a significant gap.

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 concise sentence with no wasted words. It is appropriately front-loaded, though it lacks structural richness (e.g., sections or examples) that might be expected for a more complex tool.

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 lack of annotations and output schema, the description is under-specified. It does not explain what manual tracking links are, what the generated output looks like, or any constraints on parameters. This is comparable to a minimal mutation tool description and leaves substantial gaps 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?

Schema description coverage is 100% for the two parameters (type and ad_item_id), so baseline is 3. The description adds no extra meaning beyond the schema's field names and descriptions; it does not explain how the parameters relate to link generation.

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 action ('Generate'), the resource ('manual tracking links'), and the target ('an ad item'). It is specific enough to convey the core function, though it does not explicitly distinguish itself from related tracking/conversion tag tools among the siblings beyond the 'manual' qualifier.

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 other tracking-related tools in the sibling list. There are no context cues, prerequisites, or alternative tool mentions.

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