get_playoffs

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it fails to even imply read-only safety, data freshness, or behavior during the offseason. The agent has no information about side effects, authentication needs, or potential errors.

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 concise at 11 words and front-loads the purpose. However, the ambiguous 'or' could have been clarified without much extra length, so it is slightly less effective than it could be.

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 description is incomplete for an agent to confidently invoke the tool. It does not resolve the bracket vs. standings ambiguity, lacks output schema, and does not differentiate from get_standings. The single parameter is well-defined, but overall context is missing.

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 schema already fully covers the 'league' parameter with an enum and description, so the description does not need to add meaning. Since coverage is 100%, the baseline of 3 applies, and the description provides no additional parameter insight.

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 identifies the tool as retrieving playoff information with the verb 'Get' and resource 'playoff'. However, the phrase 'bracket or playoff picture/standings' introduces ambiguity about whether one or both are returned, and it does not distinctly separate from the sibling tool get_standings.

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 provided on when to use this tool versus siblings like get_standings or get_scoreboard. There is no mention of postseason context, prerequisites, or circumstances where this tool is preferred over alternatives.

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