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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read operation by saying 'Recent runs,' but says nothing about permissions, pagination, retention limits, or what a run record contains. For a history-retrieval tool with zero annotation coverage, this is a significant gap.

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?

The description is a single front-loaded phrase with no filler or redundancy. It is efficient, though its brevity contributes to the overall under-specification of the tool.

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?

The tool has three required parameters and no output schema, so the description should explain the return shape and scope. It only says 'Recent runs' without defining how many runs, whether they are filtered by project/env, or what fields each run includes. This is insufficient for a history-list operation.

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 67%: env and project have descriptions, but name does not. The description adds no parameter-level meaning; it does not say that name identifies the cron job or that project/env scope the job. It fails to compensate for the undocumented name parameter.

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 identifies the resource and scope ('Recent runs of a cron job'), so an agent can infer it returns run history. However, it lacks an explicit verb and does not distinguish itself from the singular sibling cron.run or explain how it differs from cron.list. This is adequate but vague.

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 guidance on when to use this tool versus cron.run, cron.list, or other cron-related siblings. The description does not mention prerequisites, when-not-to-use, or alternative tools for inspecting run history.

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