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

Annotations already declare readOnlyHint=true, and the description adds the meaningful behavior that results are paginated by cursor and maps to the Project API endpoint GET /workflows/runs. It does not disclose ordering (newest first?), a default page size, or whether runs across all workflows or one workflow are returned.

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 short sentences, zero filler, with the core action front-loaded and pagination plus endpoint tacked on compactly.

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?

There is no output schema, so an agent gets no description of what a 'workflow run' record contains or its ordering, which matters for a history-listing tool. Given only three cursor-style parameters and read-only annotations, the definition is adequate but leaves the return-value shape implicit.

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 each cursor parameter is self-documented in the schema, so baseline is 3. The description's 'cursor pagination' phrasing corroborates the schema but adds no format details, default limit, or cursor lifetime beyond what is already there.

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 ('List workflow runs') plus a parenthetical scope clarification ('execution history'), which distinguishes it from get_workflow_run and list_workflows. It does not explicitly name a sibling, but the singular/plural and get/list split makes the intent unambiguous.

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 gives no when-to-use guidance, no statement of when to prefer get_workflow_run over this history listing, and no prerequisites. The cursor-pagination note is a mechanism detail, not usage direction.

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