leader_schedule

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

Discloses 'Read-only' and describes behavior (no leader slot within min_window_minutes). Without annotations, more detail (e.g., pagination, rate limits) would improve transparency.

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 concise sentences, front-loaded with key info, no wasted words.

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?

Covers purpose and one parameter, but lacks explanation of 'name' parameter and output format. Given output schema exists, more context on return values would help.

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 0%, but description only explains 'min_window_minutes' partially. 'name' parameter is not explained (assumed validator identity), leaving ambiguity. For 2 parameters, insufficient.

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?

Clear verb 'Upcoming' and specific resource 'leader slots for a validator', with explicit purpose 'whether it's safe to restart now'. Distinguishes from sibling tools like 'restart' and 'node_detail'.

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?

States it 'helps plan restarts/upgrades without skipping your own slots', implying when to use. Lacks explicit when-not or alternatives, but clear enough for context.

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