list_pa_indicators

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is established. The description adds no further behavioral details such as pagination, default filtering, or response shape. The phrase 'available in the instance' slightly extends context but does not disclose behavior beyond what annotations or schema imply.

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 a single, front-loaded sentence with zero wasted words. It immediately states the action and target resource, making it highly scannable and easily understood.

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 operation with no output schema, the description is sufficient. It conveys the purpose and scope, and the schema provides all parameter details. The annotations cover safety, so the agent has enough information to select and invoke the tool correctly without ambiguity.

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% for all four parameters (limit, query, active, category), each with a clear description. The tool description itself does not add any additional parameter semantics, so the baseline of 3 applies since the schema does the heavy lifting.

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 uses a specific verb 'List' with a clear resource 'Performance Analytics (PA) indicators (KPIs)' and scope 'available in the instance'. This clearly distinguishes it from sibling tools like get_pa_indicator (singular fetch) and list_pa_breakdowns/list_pa_dashboards (other PA entities).

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 context is clear: this tool is for listing all PA indicators available in the instance, which implies use when you need a collection of KPIs. It doesn't explicitly mention alternatives or exclusions, but the 'list' nature and sibling names provide sufficient context without being misleading.

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