Watchlist

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

The annotation already declares readOnlyHint=true, and the description reinforces this with 'Read-only: fetches current state and changes nothing.' It adds useful behavioral context beyond the annotation by clarifying that watching a player has no effect on squad or budget, which helps the agent understand side effects.

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 compact, front-loaded with the core purpose, and each sentence contributes meaningful guidance. The read-only sentence slightly overlaps with the annotation but adds plain-language clarity without bloating the definition.

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 zero parameters, an output schema, and a readOnlyHint annotation, the description covers everything needed to invoke the tool correctly: what it returns, what it does not affect, and which sibling covers the related need of sale status.

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 there is nothing for the description to clarify beyond the schema. The first sentence confirms the resource being fetched, and the rest of the description adds scope and context where parameter documentation would otherwise be needed.

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 and resource: 'Get the players the manager is keeping an eye on.' It clearly identifies what a watchlist is and distinguishes it from related tools like get_squad or get_market, so an agent can tell what it returns.

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 provides clear context ('a shortlist, not a commitment') and explicitly points to get_market as the alternative when the agent needs to know which players are actually for sale. It lacks an explicit 'do not use this for X' statement, but the guidance is sufficient for correct routing.

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