get_team

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

No annotations provided, so burden falls on description. Does not indicate side effects, read-only nature, permissions needed, or return value. 'Get team details' implies a read operation but explicitly states no behavioral 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?

Single sentence, no filler, directly to the point. Could be expanded slightly, but for a simple tool this is very concise. No unnecessary words.

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 no output schema, the description should summarize return values. It does not. Also lacks any constraints or context about team details scope. For a simple tool, it is incomplete.

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% (teamId described as 'Team ID'). Description adds no additional meaning beyond the schema; baseline 3 applies as schema already documents the parameter adequately.

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?

Clearly states 'Get team details', identifying the verb (get) and resource (team). However, it does not differentiate from other get tools (e.g., get_user, get_project). Tool name reinforces the action, so it's clear but generic.

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 on when to use this tool vs alternatives like list_teams. Does not mention any prerequisites or context. The description is purely functional with no usage direction.

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