pods

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

The description only lists variable names and an example. It discloses no behavioral traits such as return format, permissions, pagination behavior, or side effects. Since no annotations are provided, the description carries the full burden, and this is a major omission.

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 front-loaded with 'Access Groups · query pods' and then provides an illustrative example. It is reasonably concise, though the example is long and truncated. Every sentence earns its place, with no redundant fluff.

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?

Without an output schema, annotations, or a description of return values, the tool is underspecified. The example gives some context for the filter input, but the overall behavior (what is returned, pagination, errors) is missing, making it inadequate for a 6-parameter query tool.

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 100%, so the baseline is 3. The description adds a concrete example showing the nested filter structure (accessGroups, customers, ids, name, roles, users), which provides some semantics beyond the generic GraphQL type labels in the schema. However, it does not explain each parameter's purpose in depth.

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 states 'query pods', a clear verb+resource combination, and 'Access Groups' indicates a filtering context. It distinguishes from the singular 'pod' tool and mutation siblings like create_pod/update_pod/delete_pod. However, it lacks explicit mention of list/pagination semantics.

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 usage guidance is given. The description does not say when to use this tool over the singular 'pod' or other query tools, nor does it mention exclusions or alternatives. The 'query' phrasing implies read-only, but this is not explicit.

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