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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries the burden of explaining the mutation. It does disclose that this is an immediate action affecting all enabled pay run schedules, which is useful. But it does not mention side effects beyond generating drafts, idempotency, or whether generated drafts can be modified or undone.

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 two sentences with no filler. The most important information—'Generate the next monthly pay run draft(s) right now'—is front-loaded, and the scope statement follows efficiently. Every sentence earns its place.

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?

For a zero-parameter trigger tool, the description is largely complete: it states the action, the timing, and the scope (all enabled schedules). Since there is no output schema, a note about what the caller receives after triggering would improve completeness, but the core invocation context is adequately covered.

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?

The tool has zero parameters and schema coverage is 100%, so the schema fully captures the parameter surface. The description adds no parameter details, but none are needed. A baseline of 4 applies for a zero-parameter tool.

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 clearly states the action: 'Generate the next monthly pay run draft(s) right now, without waiting for the schedule.' It names a specific resource (pay run drafts) and makes the immediate-trigger nature explicit. It also distinguishes itself from waiting for the schedule and from sibling trigger tools targeting recurring contracts/invoices.

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 conveys when to use the tool: when pay run drafts should be generated immediately rather than waiting for the normal schedule. It also scopes behavior to 'every enabled pay run schedule the business has.' However, it does not explicitly mention alternatives or exclusion conditions, though the conditions for use are reasonably clear.

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