get_pricing_changesRetrieve the append-only change log of pricing updates, model deprecations, and verification events. Useful for detecting price changes since a previous check. Defaults to the last 30 days.
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | ISO 8601 timestamp; return changes at or after this time |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the append-only nature (implying read-only), the default time window, and the types of events included. It doesn't cover response format or error behavior, but for a simple retrieval tool it offers solid context.
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 concise sentences, front-loaded with the primary purpose and key details. Every sentence adds useful information without redundancy.
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 simple single-parameter read tool, the description adequately covers purpose, usage, and default behavior. It doesn't explain the response shape, but no output schema exists and the term 'change log' implies a list. Sibling differentiation is clear.
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?
The only parameter 'since' has 100% schema description coverage, so the baseline is 3. The description adds value by stating that omitting the parameter defaults to the last 30 days, which clarifies the semantics beyond the schema's 'at or after this time.'
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 uses the specific verb 'Retrieve' and clearly identifies the resource as an 'append-only change log of pricing updates, model deprecations, and verification events.' This precisely distinguishes it from siblings like compare_providers and estimate_video_cost, which serve different purposes.
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?
It states 'Useful for detecting price changes since a previous check,' giving a clear use case, and notes the default 30-day window. However, it does not explicitly mention when not to use this tool or name alternatives, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a clearly distinct purpose: compare_providers returns raw pricing rows, estimate_video_cost provides computed cost estimates with assumptions, and get_pricing_changes tracks updates over time. There is minimal overlap, and descriptions make the separation obvious.
All tool names follow a consistent verb_noun pattern: compare_providers, estimate_video_cost, get_pricing_changes. The naming is predictable and clearly indicates the action and object.
Three tools is appropriate for the narrow, focused purpose of video generation cost estimation. Each tool fills a necessary role without redundancy or bloat.
The tool set covers the core needs of the domain: listing raw pricing data, computing cost estimates, and tracking changes over time. There are no obvious gaps for the stated purpose of cost estimation.