photoshop_get_capabilities

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

Description discloses return format JSON with version and features, states preconditions: none and side effects: none. No annotations are provided, so the description carries the behavioral burden; it adequately covers safety and idempotence, though it could mention network/host overhead or failure modes.

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?

Well-structured with clear headings for use, non-use, return format, preconditions, and side effects. Each line adds value and the essential context is front-loaded.

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?

Given zero parameters and no output schema, the description provides enough for an agent to call it correctly and interpret the result. Minor gap: what happens if Photoshop is not running or the call fails isn't specified, but for a capability discovery tool this is acceptable.

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, so there is no parameter ambiguity. The description explains what is returned, effectively compensating for the absence of schema details.

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?

Description clearly states it returns 'version-aware feature flags for the installed Photoshop' with specific example features. This is a specific verb and resource that distinguishes it from siblings like photoshop_get_version and photoshop_ping.

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?

Explicitly says 'Use when: once per session before suggesting AI-powered features or gated recipes' and 'Do NOT use when: Photoshop version is already known from photoshop_get_version.' This provides clear when-to-use guidance and names the alternative.

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