ping

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

No annotations are provided, so the description carries the full burden. It states the tool tests connectivity, which implies it's a read-only diagnostic operation with no side effects. However, it doesn't specify what 'connectivity' entails (e.g., network, extension handshake), what success/failure responses look like, or any rate limits. The description adds basic behavioral context but leaves important details unspecified.

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, efficient sentence that immediately communicates the tool's purpose. Every word earns its place: 'Test' (verb), 'connectivity' (what's being tested), 'with After Effects CEP extension' (context). There's no redundancy or unnecessary elaboration.

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 the tool's simplicity (zero parameters, no output schema, no annotations), the description is reasonably complete for its diagnostic purpose. However, it doesn't specify what constitutes successful connectivity testing or what the response format might be. For a connectivity test tool, some indication of expected outcomes would enhance completeness.

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 schema description coverage is 100%. The description doesn't need to explain any parameters. It appropriately focuses on the tool's purpose without unnecessary parameter discussion. A baseline of 4 is appropriate for zero-parameter tools with complete schema coverage.

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 the tool's purpose with a specific verb ('Test') and resource ('connectivity with After Effects CEP extension'), distinguishing it from all sibling tools which perform various creative/editing operations in After Effects. It precisely communicates a diagnostic function rather than a content manipulation task.

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 description explicitly indicates when to use this tool: to test connectivity. This implies it should be used for verification purposes, likely at startup or when troubleshooting, rather than for regular editing workflows. The context clearly differentiates it from all sibling tools that perform actual After Effects operations.

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