League and standings

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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description elaborates on the scope (settings, lineup slots, waiver rules, standings) but does not describe data freshness, whether standings are current, or any open-world variability implied by openWorldHint. No contradiction with annotations exists.

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 first sentence is front-loaded and compact, listing the action and resources in a single line. The second sentence ('Team ids identify ESPN fantasy teams.') is tangential for a zero-parameter tool, so it is not fully earning its place, though it is brief and not seriously distracting.

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 zero-parameter, read-only tool with a provided output schema, the description adequately explains what the tool does and when it is relevant ('before managing a team'). It does not explicitly distinguish itself from all siblings, but the listed league-level resources make the distinction clear enough for an agent to select it appropriately.

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 rubric baseline is 4. The input schema is empty and schema coverage is 100% vacuously; the description adds no parameter-specific meaning, and none is needed. The 'Team ids' sentence is broader domain context rather than parameter documentation.

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 uses a specific verb ('Inspect') and names concrete resources: league settings, lineup slots, waiver rules, and team standings. This clearly distinguishes it from sibling tools like get_roster, get_matchups, or get_transactions, which focus on other data domains.

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 phrase 'before managing a team' gives clear contextual timing for when this read-only overview should be used. However, it does not explicitly name when-not situations or direct the agent to alternatives such as get_roster or get_matchups, stopping short of full exclusion guidance.

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