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 of behavioral disclosure but only implies read-only access through the verb 'Lists'. It fails to describe what data is returned, whether the operation is idempotent, or any rate limiting, despite the existence of an output schema that could have been referenced.

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 consists of a single efficient sentence with no wasted words. However, the extreme brevity becomes a liability given the complete absence of schema descriptions and annotations, resulting in insufficient documentation rather than effective conciseness.

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 parameter schema coverage and no annotations, the description is incomplete. While the output schema presumably covers return values, the undocumented pid parameter, lack of usage guidelines against similar retrieval tools, and absence of behavioral details leave critical gaps for correct invocation.

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?

Schema description coverage is 0%, requiring the description to fully compensate for both parameters. It only implicitly documents module_id by referencing 'module ID', while the pid parameter is completely unexplained, leaving half of the required inputs semantically undocumented.

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 uses a specific verb ('Lists') and resource ('script buttons') with clear scope ('for a specific module ID'). It implicitly distinguishes from sibling mutation tools like delete_script_button and update_script_button by operation type, but does not explicitly contrast with similar retrieval tools such as get_pynet_ui_layout.

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 guidance is provided on when to use this tool versus alternatives, or what prerequisites are needed for the module_id. The description lacks information on how to obtain valid module IDs or when to prefer this over get_pynet_ui_layout for UI layout data.

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