Contract Testing: Admin List Teams

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds workspace scope and the admin requirement, but it does not clarify how pagination behaves or whether 'all teams' means all records across pages or just the default page's results. No contradiction with annotations exists.

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 short and reasonably organized, but the 'Toolset: Admin' line largely duplicates the title/name, and the parameter section duplicates the input schema exactly. The core purpose sentence is front-loaded and clear, but some content does not add value beyond structured fields.

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 simple read-only list operation with fully documented parameters and safety annotations, the description is mostly adequate. The main gap is the potential contradiction between 'List all teams' and the default page/size behavior, which is important for an agent to know whether a single call returns all teams or only a page. There is also no indication of what the response shape will be, and no output schema is present.

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%, so the schema already documents q, page, and size with defaults and meanings. The description simply repeats the parameter list and defaults without adding extra semantics such as filtering behavior, maximum page size, or how q is matched against team names.

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 states a clear verb-resource pair: 'List all teams in the workspace (admin)'. It distinguishes the operation from related siblings like admin_get_team (single team) or admin_list_team_users (team members) by indicating the resource is teams and the scope is all teams. However, it lacks an explicit boundary like 'no filtering' and relies partly on the title/name for differentiation.

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 is provided on when to use this tool versus alternatives such as admin_get_team, admin_create_team, or admin_list_team_users. The phrase '(admin)' hints at privilege requirements but does not state usage conditions, prerequisites, or when another team-related admin tool should be preferred.

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