Sleeper account

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the operation is known to be safe and externally dependent. The description adds useful context about stable IDs and configuring a username, but does not disclose error handling or what happens when the username cannot be resolved.

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?

One sentence with no filler, front-loaded with the main verb and resource. Both clauses ('resolve...' and 'return...') earn their 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?

For a single-optional-parameter, read-only account tool, the description conveys enough to select and invoke it: it resolves an identity and returns a current state. The lack of an output schema makes the vague 'current NFL state' a minor gap, but not a blocking one.

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 100% and the only parameter is documented as an optional override for SLEEPER_USERNAME. The description adds the notion of a configured default username, but it doesn't clarify precedence or behavior if both the configured value and override are absent.

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 names a specific action (resolve username to stable user ID) and a second outcome (return current NFL state), which sets it apart from league- and roster-focused siblings. However, 'current NFL state' is vague enough that an agent won't know exactly what data to expect.

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?

No guidance is given about when to choose this tool over siblings like sleeper_list_leagues or sleeper_trade_context. The description implies the configured username is the default, but does not explain when to call this first vs other account/league tools.

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