fanduel_racing_call

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

No annotations provided, so the description carries full burden. It discloses that queries are server-side and that boilerplate variables default automatically, but does not mention whether the tool is read-only, authentication requirements, rate limits, or error handling 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?

The description is two sentences plus a resource reference, all concise and front-loaded. Every sentence adds value: defines action, explains server-side query and default variables, and directs to available operations.

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 generic GraphQL call with 2 params and no output schema, the description covers the endpoint, server-side query, default variables, and operation reference. It omits return format details, but that is operation-dependent. Could mention when to use dedicated sibling tools, but that is more for usage guidelines.

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 coverage is 0%, so description must compensate. It explains the 'operation' parameter as a GraphQL operation name and 'variables' as optional, with a note that they often default. It points to an external resource for operation list and variable signatures, adding value beyond the schema.

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 clearly states 'Call any FanDuel Racing (TVG) GraphQL operation by name + variables', with specific verb, resource (FanDuel Racing GraphQL), and scope (any operation). It distinguishes from siblings like 'fanduel_sb_call' by specifying the Racing domain.

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 mentions reading 'fanduel://racing/operations' for the operation list and variable signatures, which indicates where to find valid operations. However, it does not explicitly state when to use this tool versus dedicated siblings (e.g., 'fanduel_racing_messages', 'fanduel_racing_promotions') or provide exclusion criteria.

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