get_league_settings

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by describing a static league format and advising a single call, but it does not explicitly state that it has no side effects or that it can be called safely multiple times. The note about calling once suggests idempotence, but not explicitly. A getter typically needs to disclose read-only status, which is absent.

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, front-loads the core content (what the tool returns), and then gives usage guidance. There is zero waste; every sentence earns its place.

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 parameters and no output schema, the description must explain what the tool returns and when to use it. It lists the key attributes and explains the foundational nature of the tool. This is complete for a zero-parameter getter with no side effects.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter-specific information, but none is needed. It correctly avoids redundant content.

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 explicitly states the tool returns league format details (team count, scoring rules, starting lineup, draft type). This is a clear, specific resource that distinguishes it from siblings like get_draft_state or get_roster, which deal with different aspects of the draft.

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?

It explicitly instructs to call this once at the start of a session and explains why: every other tool's numbers are relative to this league's shape. This provides clear timing and dependency guidance, making it obvious when to use this tool over alternatives.

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