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

Annotations already cover readOnly, openWorld, idempotent, and destructive traits, so the bar is lower. The description does add a behavioral constraint (the 50M cell limit) that is not in the annotations, which is useful. However, it does not mention return format, pagination, or error behavior, so it adds only limited additional transparency.

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 compact single sentence that leads with the action and limit, then defines the two parameters. There is no redundancy or filler; each clause contributes essential information.

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 only two parameters, both fully described in the schema, and rich annotations, the description is complete. It discloses the cell limit, defines the parameters, and the schema example covers the output format, so no critical information is missing 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?

With 100% schema coverage, the baseline is 3. The description enriches parameter understanding by using domain vocabulary: 'path is the .px table id' and 'body is a PxWeb query object.' This clarifies the semantic purpose of each parameter beyond the structural schema descriptions and example.

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 a specific action ('Pull data from a table') with a concrete resource and a notable constraint (max 50,000,000 cells). It also names the two parameters and their roles, which helps distinguish it from sibling tools like table_meta that likely provide metadata rather than data.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor does it mention any sibling tools or exclusion conditions. The description simply defines the operation; an agent must infer usage context entirely from the tool name and purpose.

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