get_team_members

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

No annotations present, so description carries burden. Discloses default flattened output shape and raw parameter effect. Mentions key is same as worker field. Does not address pagination or idempotence, but for a read-only list tool, the provided details are sufficient.

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?

Description is well-structured with clear sections. Includes URL, parameter explanations, and usage notes. Could be slightly more concise (e.g., floating the URL), but overall efficient and readable.

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?

Output schema exists, so return value details are not needed. Description covers default vs raw output and key mapping. Given sibling tools context, it provides enough information. Could mention pagination, but not essential.

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 coverage is 0%, but description fully compensates. Explains team_id with data type and example (79). Explains raw parameter with its purpose and when to use it ('when you need fields not surfaced by default'). Adds meaning beyond raw schema.

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 'List all members of a Tempo team' with specific verb and resource. Distinguishes from 'get_all_users' by noting Tempo team vs Jira user group. References exact API endpoint: rest/tempo-teams/2/team/{team_id}/member/.

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?

Explicitly says when to use this tool ('List all members of a Tempo team') and when not ('not a Jira user group'), with alternative tool named ('see get_all_users for groups'). Additionally explains that the output 'key' field is used in per-user worklog tools, providing integration guidance.

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