pinterest_get_billing_and_orders

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

With no annotations, the description carries the burden of behavioral disclosure. It does state that the tool is read-only and that financial data is returned only when the token has account access, which is useful. However, it does not explain what happens without access, pagination behavior, or mode-dependent behaviors, leaving significant gaps.

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 two tight sentences with no filler. It front-loads the tool's core purpose in the first sentence and adds a key access caveat in the second. Every word earns its place.

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?

This is a complex tool with 6 parameters, 9 mode enum values, a nested query object, and no output schema or annotations. The description covers only the broad resource types and an access condition, leaving out critical operational details such as required parameters per mode, response shape, and pagination behavior. It is not adequate for reliable 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?

Schema description coverage is low at 33%, and the description does not compensate by explaining how the listed resources map to the `mode` parameter or how `query`, `entityId`, and `pageSize` should be used. The description adds almost no meaning beyond the schema, leaving the agent to guess parameter semantics for most options.

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 tool's scope with a specific verb ('Read') and enumerates the resources involved: billing profiles, invoices, order lines, ads-credit discounts, and SSIO account/order status. It is unambiguous about what the tool does, but it does not explicitly differentiate it from sibling tools, so it falls short of a 5.

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 guidance is given about when to use this tool versus siblings like pinterest_get_account_entities or pinterest_get_business_assets. The only contextual note is about token access, which is a requirement rather than a usage-selection guideline. There are no exclusions or alternative conditions.

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