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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely useful behavioral context beyond that: the ROI sign convention (0.25 = +25 percent), the meaning of roi_ex1, and default tier/scope/min_lineups behavior reducing result sets.

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?

It is a dense single-block run-on rather than a scannable structure, and the view breakdown, defaults, and ROI convention are all crammed together. The content is largely justified, but the lack of formatting makes it harder to parse than its length alone would suggest.

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 11 optional parameters, no output schema, and no required fields, the description does the work needed: it enumerates what each view returns, states defaults, and clarifies ROI units. It could note result-ordering or pagination behavior, but it is otherwise sufficient to invoke the tool correctly.

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%, so the baseline is 3. The description goes further by mapping view values to returned fields and explaining the fractional ROI convention, which the schema does not. Parameters like team, player, and sort_by are left to the schema, keeping it modest but above 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 states a specific resource (NFL DFS contest ROI graded by BankrollSZN) and breaks it into three named views (players, builds, contests) with the metric each returns. An agent immediately knows this retrieves DFS ROI rather than projections or ownership. It does not explicitly distinguish itself from adjacent siblings like invoke_nfl_ownership_by_contest, so it lands at 4 rather than 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?

Describing what each view returns (players = per-player ROI/cash/share; builds = ROI by stack/bringback/flex/spend; contests = graded contest list) gives clear context for choosing the view parameter, and defaults for tier/scope are stated. There is no explicit when-not guidance or named alternative tools, so it stays at 4.

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