list_pan_elements

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get all' implies a read-only operation, it doesn't mention pagination behavior (despite offset/limit parameters), rate limits, authentication requirements, or what 'all' means in practice (e.g., recursive vs flat listing). This leaves significant gaps for a tool with 12 parameters.

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, clear sentence that states the core purpose without unnecessary words. It's front-loaded with the essential information ('Get all elements and folders') and contains no redundant or verbose phrasing.

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 tool with 12 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'elements' include (e.g., APIs, collections, workspaces), how folders are structured, whether results are paginated, or what the return format looks like. The agent must rely entirely on the input schema and trial-and-error.

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 100%, with each parameter well-documented in the schema itself. The description adds no additional parameter information beyond implying a listing operation. This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't enhance understanding of how parameters interact or their practical use.

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 verb ('Get') and resource ('all elements and folders in Private API Network'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_tagged_elements' or 'list_apis' that might retrieve similar resources, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools that retrieve API-related resources (e.g., 'list_apis', 'get_tagged_elements'), there's no indication of when this specific listing is appropriate, leaving the agent to guess based on context.

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