find_team

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

Discloses local filtering behavior and case-insensitivity. No annotations provided, so description carries full burden — it reveals the underlying implementation (no server-side search) without contradicting any metadata.

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?

Five lines with clear structure: purpose first, then behavioral context, then usage hint, then parameter details. Every sentence adds value and no redundancy.

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?

Covers purpose, behavior, parameter semantics, and use case. Could mention handling no results or errors, but given output schema exists and tool is simple, this is adequate.

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?

Both parameters are described in args: 'query' as substring match to team name, 'expand' as optional comma-separated expand fields with example. Schema had 0% coverage, so description fully compensates.

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 'Find Tempo teams whose name contains query (case-insensitive)' — specific verb, resource, and matching rule. Distinguishes from siblings like get_all_teams (lists all without filtering) and search_users/search_groups.

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?

Explains that no server-side search exists, so tool lists all teams and filters locally. Provides a concrete use case: converting team name to teamId for get_team_worklog. Lacks explicit 'when not to use' but context is sufficient.

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