Query a PSA OpenSTAT dataset

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds a critical behavioral warning: PXWeb expands unselected dimensions and PSA returns HTTP 403 for full-cube requests. This goes beyond annotations by explaining a failure mode and the reason for the strict requirement.

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, immediately front-loaded with the purpose. Every clause adds critical information: bounded query, need for explicit codes, failure mode. No 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?

With an output schema present, return values don't need description. The tool has only 3 parameters, and the description covers its essential behavior, the companion tool to use first, and the key failure condition. It is self-contained and sufficient for an agent to invoke correctly.

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 value by emphasizing that selections must cover every dimension and pointing to describe_psa_dataset as the source of valid value codes. This supplements the schema and helps the agent construct correct selections.

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 opens with 'Run one bounded query against a PSA OpenSTAT dataset,' which names a specific verb and resource. It clearly differentiates from siblings like browse_psa_catalog and describe_psa_dataset by focusing on query execution against a dataset.

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 gives concrete guidance: 'Every dimension needs an explicit list of value codes from describe_psa_dataset.' It also frames this as a hard requirement, telling the agent to first call describe_psa_dataset. It stops short of explicitly naming alternatives or exclusions, so it doesn't earn a 5.

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