Px Capabilities

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

No annotations are provided, so the description carries the disclosure burden. It reveals that the tool is informational, that Retro Diffusion availability is conditional, and that gating behavior is explained. It also tells callers how to fetch image content back. It does not explicitly say 'read-only' or 'no side effects,' but the overview framing and zero-parameter signature make that implicit.

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 sentence with a colon-delimited list, front-loading 'One-call overview' to immediately establish purpose. Every phrase earns its place, and the structure makes the covered topics scannable. No filler or repetition.

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?

The output schema covers return values, and the zero-parameter signature simplifies invocation. However, the description claims to overview 'what this server can currently do' yet only names Aseprite and Retro Diffusion, omitting the Krita subsystem visible among the sibling tools. This creates ambiguity about whether the overview is truly server-wide or scoped to specific subsystems.

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 is empty with zero parameters, so there are no arguments to document. The description adds meaning by scoping what the tool returns rather than needing to explain parameters. This is the appropriate baseline for a zero-parameter 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 clearly states a specific meta-purpose: provide a one-call overview of server capabilities, specifically Aseprite and Retro Diffusion availability, gating behavior, and image-fetching mechanics. This distinguishes it from the operational sibling tools even though no sibling is named. The verb 'overview' plus the resource 'what this server can currently do' is specific and useful.

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 'one-call overview' phrasing clearly implies use for capability discovery and orientation before selecting an operational tool. However, it never explicitly states when to prefer this over subsystem status tools or when not to use it, and no alternatives are named. Context is clear, but exclusions are absent.

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