draft_sync_yahoo

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

The description asserts 'Idempotent,' while the annotations declare idempotentHint=false – a direct contradiction about a behaviorally significant property (whether repeat calls are safe). 'Read-only toward Yahoo' is defensible against readOnlyHint=false only because the tool writes local draft state, but the idempotency claim is a straight conflict with structured data.

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 tight sentences that front-load the core action, then the return contract, then the failure mode. No filler, though the trailing clause about pending Yahoo access could be folded more economically.

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 carries the return-value burden and does it well: new picks, on-the-clock status, and recommendations. It also discloses the pending-API failure mode. The undocumented 'top' parameter and the unaddressed idempotency conflict keep it from being fully complete.

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?

There is one parameter, 'top', with 0% schema description coverage and no default explanation beyond '8'. The description never mentions it, though 'recommendations when it's my turn' hints obliquely at what the parameter governs. With a documented parameter and no compensating text, this falls below the 3 baseline.

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 uses a specific verb+resource: 'Read the league's Yahoo draft results and record every new pick ... into the live draft state.' That dual read-source/write-target scope is clear. It separates itself implicitly from siblings like draft_pick and draft_start, though it never names them explicitly, which keeps it just short of a 5.

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?

It gives one piece of situational context – 'errors clearly while Yahoo API access is pending' – which tells the agent when the tool will fail. But it never states when to call this versus draft_pick, draft_start, or draft_recommend, so the routing decision is left to inference.

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