get_team

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

Annotations already declare readOnlyHint and idempotentHint. The description adds useful behavioral context by stating what information is returned ('display name, abbreviation, and location') and clarifying the ID source, without contradicting annotations.

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 and well-structured: a purpose sentence, a return-content sentence, and an Args section. Every sentence earns its place, with no redundant information.

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?

With a single parameter, an output schema present, and comprehensive annotations, the description provides all necessary context for correct selection and invocation. The tool is simple, and the description covers purpose, parameter, and return expectations.

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 has 0% description coverage for team_id, but the description fully compensates by explaining 'ESPN numeric team ID' and providing an example ('18418' for Atlanta United FC). This clearly conveys both meaning and format.

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 'Get details for a specific Women's Super League team' with a specific verb and resource. It distinguishes from the sibling get_teams by emphasizing 'specific', implying get_teams is for lists.

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?

Provides explicit context: 'Use the numeric ID returned by get_teams' establishes a prerequisite and ties it to the sibling tool. However, it does not explicitly state when not to use other alternatives, though this is implied by 'specific'.

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