Get My Status

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

No annotations are provided, so the description carries the full behavioral burden, and it only lists returned fields. It says nothing about permissions, whether league_id omitted means 'current league', error behavior if the user is not in a league, or freshness of the figures. With an output schema present, the field list adds little beyond structured data.

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?

A single front-loaded sentence with no filler; the verb and subject arrive first and every clause adds information. Nothing is redundant.

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?

The output schema covers return values, but with zero annotations and an undocumented optional parameter, the description is too thin for correct invocation. An agent still cannot tell what an omitted league_id does or how this differs from overlapping sibling tools.

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 single parameter league_id has 0% schema description coverage and is never mentioned in the description. The crucial semantics — that it is optional, defaults to null, and what null selects — are left entirely undocumented, which can lead to wrong invocations.

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?

States a specific verb and resource ('Get your status in a league') and enumerates the returned data points (budget, team value, points, placement), which lets an agent distinguish it from get_my_squad or get_my_lineup. It does not explicitly differentiate it from the closest sibling, get_league_overview, but the personal focus is clear.

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?

There is no statement of when to use this versus get_league_overview, get_my_teamcenter, or get_league_ranking, and no prerequisites or exclusions. The 'in a league' phrasing only implies that a league context is needed.

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