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

Annotations already flag this as read-only and non-destructive, and the description adds useful context: the Pro+ plan requirement and the fact that data comes from a cache rather than live systems. It could be more transparent about possible staleness or output behavior, but the provided context goes beyond the structured annotations.

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, tightly packed sentence with the access requirement front-loaded and the core operation clear. Every part of the sentence adds information; there is no redundancy or filler.

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 zero-parameter, read-only list operation, the description covers the essential information: what it lists (Power Platform connections), where it gets them (Power cache), and the access requirement (Pro+ plan). It does not explain what Power Clarity is or whether cached results may be stale, but these are minor gaps for such a simple tool.

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 tool has zero parameters and the schema has 100% coverage, so there are no parameter semantics to clarify. The description correctly implies a no-argument list operation. This matches the baseline for a parameterless tool.

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 specific action and resource: 'List all Power Platform connections,' with a clear source ('from the Power Clarity cache'). It is readable and distinguishes itself from live connection listing implicitly through the cache qualifier, though it does not explicitly name siblings or contrast with list_live_connections.

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 when-to-use or when-not-to-use guidance is provided. It does not mention alternatives like list_live_connections or explain when the cached list is appropriate instead of the live one. The only context is the Pro+ requirement.

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