euroleague_people

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

Beyond readOnly/openWorld/idempotent annotations, it alerts users that the response is ~600 KB and must be paged, and it specifies the return shape ({total,data:[...]}) and that no auth is needed. This adds operational context not present in annotations.

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?

Description is compact: two sentences plus example and auth line. The size warning is front-loaded, and every line adds value.

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?

No output schema, so the return field list is helpful. With annotations covering read-only/idempotency, schema covering all params, and description covering pagination and example, the tool is adequately specified for an agent.

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 covers all 4 parameters with descriptions (season required, limit/offset paging, competition enum). The description's example illustrates parameter usage but does not add significant new semantics beyond the schema, so baseline 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?

Description clearly states it returns 'Players and coaches registered for a season,' naming the resource (people) and scope (season). This distinguishes it from sibling Euroleague tools like euroleague_game or euroleague_seasons by content type.

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?

Provides clear context: it's for retrieving season rosters, warns about large size and recommends pagination. However, it does not explicitly contrast with sibling tools or state when not to use it, so it falls short of explicit alternatives.

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