Ping

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

A connectivity probe is inherently read-only and idempotent, yet the annotations declare readOnlyHint=false and idempotentHint=false; the description does not reconcile this tension. It does usefully tell the agent to run it as a gating step, but adds little else beyond the schema and 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?

Two short sentences, with the purpose front-loaded and the usage instruction immediately after. No filler and nothing to trim.

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-argument probe with an output schema and annotations, the description covers what an agent needs to call it correctly. The only gap is that it does not clarify how it relates to the sibling connection-verification 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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly avoids inventing parameter detail that does not 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?

States a specific verb and object: a health check that verifies the CEP plugin is running and connected to Premiere Pro. It is clear what the tool does, but it never distinguishes itself from the closely related sibling verify_premiere_connection, which an agent could reasonably pick instead.

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?

Gives explicit sequencing guidance: 'Call this before other tools to confirm connectivity.' That is a clear when-to-use statement, but it names no alternative or precondition, so the overlap with verify_premiere_connection is left unresolved.

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