get_current_leagues_by_team_id

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

With no annotations, the description must disclose behavioral traits. It states 'Get only current active leagues,' which is a read operation, but does not clarify what defines 'current active' (e.g., based on season dates) or discuss pagination, response format, or side effects. Basic transparency is present but lacks depth.

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 one short, clear sentence that conveys the essential purpose without extraneous words. It is front-loaded and efficient.

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?

Given 8 parameters (many optional), no output schema, and no annotations, the description is too brief. It does not explain what 'current active' means, how the pagination parameters work, or what the response contains. For a tool with this complexity, more context is needed.

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 input schema has 100% coverage, so the description does not need to reiterate parameter meanings. However, it adds no contextual meaning beyond the schema, such as explaining how 'include' or 'filters' interact with the league data. Baseline score of 3 is appropriate.

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 clearly states the tool retrieves 'only current active leagues for a team,' distinguishing it from sibling 'get_leagues_by_team_id' which likely returns all leagues. The verb 'Get' and resource 'current active leagues' are specific and unambiguous.

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 description implies when to use this tool over 'get_leagues_by_team_id' by specifying 'only current active leagues.' However, it does not explicitly exclude other scenarios or mention alternatives, but the context from sibling names makes the usage clear.

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