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

Annotations already declare readOnly, idempotent, and non-destructive, so the description's job is context: it correctly frames output as AI-generated (hence potentially stale) and scoped to a single competitor, and clarifies that generation is a separate in-app action. It stops short of describing the empty/unavailable-card case.

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?

Front-loaded with the verb and resource; the section list is dense but each item tells the agent what content to expect from the return. The generation sentence is a worthwhile second beat rather than filler.

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?

With an output schema handling return shape and annotations handling safety, the description covers scope, content, and the generation pathway. The only meaningful omission is behavior when the competitor has no battlecard or isn't tracked.

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 coverage is 100% and the only parameter's format ('acme.com') is fully documented there, so the schema carries the load. The description adds only the mild implication that the domain must belong to a tracked competitor.

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?

States a specific verb and resource ('Get the AI-generated sales battlecard for one tracked competitor') and enumerates exactly what the card contains, so an agent knows this is the sales-enablement view rather than the SEO, feature-gap, or matrix views its siblings return. No sibling is named explicitly, which keeps it just short of 5.

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?

'for one tracked competitor' establishes the precondition, and the closing sentence routes card creation/refresh to the app's Battlecard tab, telling the agent this tool only reads. It doesn't state what to do if the competitor isn't tracked or no card exists yet.

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