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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful scope context (DraftKings classic slate, current) but says nothing about data freshness, whether the slate must exist before calling, or how the plan limit noted in the schema behaves.

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?

A single front-loaded sentence that leads with the resource and slate before enumerating fields. The field list is long but earns its place given there is no output schema.

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 enumeration of returned metrics is genuinely valuable and covers most of what an agent needs. It still omits prerequisites (does a classic slate have to be active?), staleness of projections, and how the plan limit interacts with the limit parameter.

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 100% and all three parameters (limit, player, sort_by) are documented there, including the enum values. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

Names a specific resource (PGA DFS projections) and scopes it to the current DraftKings classic slate, which an agent can immediately act on. It does not, however, distinguish itself from close PGA siblings such as invoke_pga_optimizer, invoke_pga_strokes_gained, or invoke_pga_course_history, so an agent must infer the boundary itself.

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 states scope (current DraftKings classic slate) but gives no when-to-use or when-not-to-use guidance and names no alternative. With ~90 siblings including several PGA projection-adjacent tools, the absence of routing guidance is a real gap.

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