List App Distribution testers

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether results are paginated, what the default page size is, how the pageToken is used, or whether filtering is supported. Only the most minimal behavioral information is conveyed.

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?

A single, front-loaded sentence with no waste. It is efficient, though the brevity comes at the cost of the information the other dimensions require.

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 tool with 3 undocumented parameters, no annotations, and no output schema, the description is far too thin. It omits parameter semantics, pagination behavior, and return format, leaving significant gaps an agent must fill by guesswork.

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% with three parameters (filter, pageToken, projectId), all undocumented. The description names none of them and adds no meaning about their syntax or usage, leaving the agent with no guidance for any input.

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 a specific verb (lists) and resource (testers) scoped to a Firebase project. It is distinguishable from the mutating siblings (add_testers, remove_testers) by the verb alone, though it does not explicitly name those siblings or clarify project vs. group scoping.

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?

Usage is implied by the verb (read-only listing of testers), which fits the sibling set. There is no explicit when-to-use guidance, no mention of paging or filtering context, and no routing to alternatives like list_groups. Adequate but with clear gaps.

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