photoshop_ping

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

No annotations are provided, so the description carries the full behavioral burden. It discloses preconditions (none), return value (connection success or failure message), and side effects (may trigger Photoshop detection). A slight gap is that 'may trigger detection' is somewhat vague about what that detection entails, but it is still meaningful transparency for a ping-like tool.

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 compact and well-structured with a clear first sentence followed by short bullet-like usage, return, precondition, and side-effect notes. Every line adds information and the critical usage distinction 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?

For a zero-parameter connectivity check with no output schema, the description covers the purpose, invocation timing, alternative tool, return content, preconditions, and side effects. Nothing necessary for an agent to call this tool correctly is missing.

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?

There are zero parameters and the schema documents this fully with 100% coverage, so the baseline of 4 applies. The description correctly adds no unnecessary parameter guidance since none exist.

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 clear verb and resource: verify Photoshop is installed and reachable. It also distinguishes itself from photoshop_get_state by noting when each should be used, which is essential given the sibling list includes get_state.

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?

Explicit when-to-use and when-not-to-use guidance is provided: call once at session start if connection status is unknown, and do not call on every tool invocation. It names the preferred alternative, photoshop_get_state, leaving no ambiguity about routing.

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