score_ad_pattern

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

With no annotations provided, the description carries the full burden. It does disclose the key non-persistent behavior ('without saving it'), but it does not disclose what the scoring call returns, whether it makes external calls, or any other operation-level side effects.

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. The critical 'without saving it' qualifier is placed prominently at the end of the main clause.

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?

The purpose and non-saving behavior are covered, and the schema handles parameter documentation. However, there is no output schema, and the description does not explain what the score result looks like or how to interpret it, leaving a meaningful gap for a scoring tool.

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%, so the input schema already fully documents all 11 parameters. The description adds no parameter-specific meaning beyond framing them as aspects of a 'copied ad pattern', so the baseline of 3 is appropriate.

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 a specific action ('Score'), a specific resource ('a copied ad pattern'), and the intent ('for reusable winning signals'). It also distinguishes itself from save-oriented tools with 'without saving it'.

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?

The description makes clear this is for scoring an ad pattern rather than persisting it, which differentiates it from record_ad_swipe and list_ad_swipes. However, it does not explicitly name alternatives or state when-not-to-use it beyond the no-saving qualifier.

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