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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the default (20) and cap (100) on results, which is genuinely useful behavior. However, it does not disclose ordering of runs, and since the schema exposes no offset/cursor parameter, an agent cannot tell that results beyond 100 are unreachable without changing filters.

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, front-loaded with what is returned and scoped to whom, with the limit behavior appended. No filler or restatement of the title.

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 7 optional parameters, 71% schema coverage and no output schema, the description is thin: it never explains run ordering, whether omitting automation_id lists runs across automations, or how preferences_mode changes the result set. Adequate to call the tool, but leaves real ambiguity about what comes back.

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 71%, above the point where the schema does most of the work, so a 3 is the baseline. The description only adds the default value for limit; the more consequential parameters (conversation_id, preferences_mode, agent_preferences) are untouched, and the phrase "for an owned ... automation" implies automation_id is required when no parameter is actually required.

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 ("List") and resource ("normalized run history") scoped to "an owned lead-sourcing or trend-research automation." This distinguishes it from get_automation_run (single run) and list_automations by implication, though it never names those siblings explicitly.

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 second sentence is pagination mechanics, not usage guidance. Nothing says when to use this vs. get_automation_run for a single run, or vs. list_automations when the automation id is unknown, and there is no mention of what happens when automation_id is omitted.

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