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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description earns credit for adding non-obvious behavior: unsupported legacy records are filtered out, so an agent should not treat the result as a complete inventory. It stops short of describing pagination or ordering.

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?

Two sentences with zero filler: scope and returned fields first, then the exclusion caveat, then the usage rule. Everything is front-loaded and each clause carries distinct information.

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 no output schema, the description usefully signals the return payload (lifecycle state and recent status) and the coverage caveat (legacy records excluded). The five optional auth/preferences parameters remain entirely on the schema, but nothing critical to calling it correctly is missing.

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% and all five parameters (uid, bearer_token, conversation_id, preferences_mode, agent_preferences) are documented in the schema itself. The description adds no parameter guidance at all, so the baseline 3 applies — the schema does all the work here.

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?

Names a specific verb (List) and a precisely scoped resource (the authenticated user's lead-sourcing and trend-research automations), plus what each record carries (lifecycle state, recent status). This clearly separates it from sibling tools like list_automation_runs, get_automation_run and the create/update/delete automation tools.

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?

Explicitly frames the call as a prerequisite: 'use this before editing or deleting an automation,' which gives an agent a concrete decision rule. It does not, however, contrast itself with list_automation_runs, the closest alternative an agent might pick by mistake.

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