paloalto_send_command

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

Discloses use of PTY interactive sessions, a key behavioral trait. With no annotations, it partially fills the gap but omits details about output, errors, or side effects.

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 sentences plus examples, no fluff. Front-loaded with purpose and usage. Highly efficient.

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?

Covers purpose and usage adequately for a simple command tool, but lacks output description, error handling, or prerequisites. Given no output schema, more detail would help.

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 coverage is 0%, so description adds context for 'command' via examples. 'ip_address' is not described, but its role as the firewall IP is implicit from the purpose.

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?

Clearly states the tool executes SSH commands on Palo Alto firewalls, with specific examples like 'show vpn gateway'. Distinguishes from siblings by specifying it's for Palo Alto and from its parallel variant.

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?

Explicitly says 'USE THIS for ALL Palo Alto firewall commands', providing strong guidance. Mentions PTY session requirement but does not contrast with the parallel sibling tool.

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