apps__perf_power_metrics__list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe read operation. The description adds that it lists metrics for an app and uses a GET endpoint. However, it does not disclose pagination behavior (implied by next_url parameter) or other traits like rate limits or response format. The annotations carry most of the burden.

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 extremely concise: two sentences that state the purpose and provide the API endpoint. Every word is necessary; there is no fluff or 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?

For a simple list tool with good annotations and schema, the description is minimally adequate. However, it lacks explanation of return values (no output schema), pagination details, and explicit differentiation from the sibling build-focused list tool. The description could be improved by mentioning filters or the scope difference.

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?

The input schema has 100% coverage with descriptions for all 5 parameters, including details like the next_url parameter overriding others. The description does not add any additional meaning beyond what the schema provides. Therefore, baseline score of 3 is appropriate.

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 clearly states 'List the perf power metrics belonging to an app', specifying the verb 'List', the resource 'perf power metrics', and the scope 'belonging to an app'. It also provides the HTTP method and path, distinguishing it from sibling tool 'builds__perf_power_metrics__list' which lists metrics for a build.

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?

The description does not provide any guidance on when to use this tool versus alternatives like 'builds__perf_power_metrics__list'. There is no mention of prerequisites, context, or when-not-to-use scenarios. The agent is left to infer usage from the name and description.

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