get_team_social_media

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by explaining the structure of returned media records (type as platform, foreign_key as handle/slug/URL fragment) and the source (The Blue Alliance), which supplements the annotations with output format details.

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 two sentences long, direct, and front-loaded with the primary action. Every sentence provides necessary information without redundancy or fluff, making it highly 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 the tool's simplicity (one required parameter, no output schema), the description fully explains the return format and the types of data returned. It covers the essential information an agent needs to use the tool correctly, including the platforms and the meaning of 'type' and 'foreign_key'.

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 already provides a thorough description of the team_key parameter with pattern and format. The description does not add any additional meaning or context beyond what the schema offers, so it meets the baseline for a single parameter with full schema coverage.

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 official social media handles for a team, listing specific platforms (Twitter/X, Instagram, Facebook, etc.) and indicating the return format. It distinguishes itself from sibling tools like get_team_media by focusing solely on social media handles.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., get_team_media). It lacks explicit when-to-use or when-not-to-use instructions, leaving the agent to infer from the description alone.

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