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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that (projection source, that it returns DK ids), but says nothing about how locks/excludes affect output, whether generated lineups are persisted, or rate/latency behavior.

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 sentences, front-loaded with the core action and constraints, with no filler. The second sentence is a compact enumeration, though it borders on a run-on list.

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 the 'Returns DK ids' note is doing real work, but for a 9-parameter tool with 0% schema coverage the description should explain 'mode' (GPP vs cash strategy) and lineup-count semantics. As-is, an agent can call it but cannot reason about several knobs.

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 description coverage is 0% across 9 parameters, so the description carries the burden. It maps roughly six params (locks, excludes, unique lineups, salary floor, ownership cap, make cut floor) but leaves 'mode' (gpp/cash), 'lineups', and 'own_lambda' unexplained, and gives no array-format or value-range hints.

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+resource ('Builds DraftKings PGA classic lineups') with concrete format constraints (6 golfers, $50,000) and names the data source (BankrollSZN projections). It is clearly distinguishable from projection/odds siblings, though it does not explicitly contrast itself with the other sport-specific optimizers.

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 says the lineups are for the 'current event' but gives no when-to-use guidance, no prerequisites, and no alternatives. There is nothing telling an agent when to reach for this optimizer versus invoke_pga_projections or a different sport's optimizer.

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