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

Annotations already establish this is a safe, idempotent read, so the description's job is to add non-obvious traits — and it does: it warns that one athlete can appear in several rows (a duplicate-key hazard for consumers) and that 'salary is not a price' (a semantic caveat that prevents misuse). It stops short of describing pagination behavior or ordering despite limit/offset parameters, which keeps it from a 5.

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 very short sentences with no wasted words, and the salary caveat is placed last where it lands as a warning. However, the opening fragment is telegraphic and verbless, so brevity comes at the cost of immediate comprehension.

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 four-parameter, zero-documented-schema tool with no output schema, the description does far too little: no filter semantics, no pagination defaults, no explanation of returned fields despite referencing salaries. The duplicate-row and salary caveats partially compensate, but an agent could still call this with the wrong filter and misread results.

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%, so the description must carry parameter meaning, and it explains none of limit, offset, sport, or slate_id. The one usable hint is the 'several rows' remark, which implicitly justifies filtering by slate_id, but the agent gets no guidance on which filter to pass or how pagination bounds interact.

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 is a noun phrase ('Roster-slot draftables with salaries') rather than a verb+resource statement, so the agent must lean on the tool name to know this lists DFS players. The domain terms 'roster-slot' and 'draftables' do narrow the resource, but nothing distinguishes it from siblings like get_dfs_slates or get_dfs_contests beyond the word 'players' being absent.

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?

There is no when-to-use guidance, no mention of the slate_id parameter as the natural scoping path, and no reference to sibling tools for contests, slates, or sports. The agent gets no signal about whether this is the right call before or after fetching slates.

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