espn: Get team details

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering safety and idempotence. The description adds return content categories (record, stats, venue, next event) but omits rate limits, auth needs, pagination, or data freshness, so it provides only modest context beyond structured fields.

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?

Single front-loaded sentence with no redundant clauses. Every phrase ('detailed information', 'specific team', and the enumerated contents) earns its place.

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?

For a read-only, no-output-schema detail tool with full schema coverage and safety annotations, the description adequately states the resource and main returned data. It is slightly incomplete in not clarifying how it differs from sibling endpoints (roster, schedule, teams list), but the core need is covered.

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 description coverage is 100%, with sport, league, team_id, and fields all documented in the schema. The description adds no parameter-level detail, so the baseline 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?

States a specific verb ('Get') and resource ('detailed information about a specific team') with enumerated contents (record, stats, venue, next event). However, it does not distinguish itself from sibling tools like espn_get_team_roster, espn_get_team_schedule, or espn_get_teams, so the agent must infer the boundary.

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 when-to-use guidance, no alternatives named, and no exclusions. The description only states what the tool returns, leaving the agent to infer that this is for a single team's detail view rather than roster, schedule, or list endpoints.

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