PyNet Bridge

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

With no annotations provided, the description carries the full burden. 'Handshake ping' implies a lightweight, read-only connectivity check, but the description omits failure modes, timeout behavior, or what constitutes 'responsive' versus unresponsive.

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?

Single sentence, efficiently front-loaded with no redundant words. Every term ('Handshake', 'ping', 'plugin listener', 'responsive') contributes meaningful information about the tool's function.

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 has an output schema (covering return values) and only one parameter, the description adequately covers the conceptual purpose but is incomplete due to the total absence of parameter documentation and lack of behavioral details that annotations would normally provide.

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 schema has 0% description coverage (only 'title': 'Pid'), and the description fails to compensate by explaining what 'pid' represents (process ID, plugin ID, etc.) or how to obtain it. The parameter is completely undocumented in natural language.

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 identifies the action ('Handshake ping') and target ('plugin listener'), specifying it checks responsiveness. It distinguishes from siblings like get_output_window_status by specifying 'plugin listener' rather than other components.

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?

No explicit guidance on when to use this versus sibling tools like get_output_window_status or list_active_instances. No mention of prerequisites or conditions where this check is preferred.

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