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

No annotations are provided, so the description carries the full behavioral burden. It states the tool produces aggregate data, but never says whether the stage persists results or is purely computational, what permissions are required, whether it is idempotent, or what the caller gets back — despite the presence of a dry_run flag implying real 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?

Three short sentences, front-loaded with the action and scope, with no filler. The final sentence restating the stage_type values is mildly redundant with the schema enum but costs little.

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 should clarify the return shape and execution side effects, but only says 'aggregate data and statistics.' It also omits how this stage relates to pipelines/templates, leaving the agent to guess at the execution context.

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 schema already documents assets, config, dry_run and stage_type. The description repeats the stage_type enum values and says nothing about config shape, adding no meaning beyond what the structured schema provides.

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 gives a specific verb (Execute), resource (SUMMARIZE-category pipeline stage) and scope (a set of assets), and states the outcome (aggregate data and statistics). It is clearly distinguishable from read-oriented siblings like GetAssetDetails, though it never explicitly says which sibling to prefer.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as ListPipelines or GetExperimentSummary. The agent must infer that this is the tool for computing summaries over asset sets.

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