pro_usageCurrent month API usage: quota, vehicles consumed, remaining, extra credits. Quota mensuel de véhicules du plan, consommé, restant et crédits achetés.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already indicates this is a safe read operation. The description adds some context by specifying the scope (current month) and the metrics included, but it does not disclose additional behavioral traits such as authentication requirements, timezone details, or the meaning of 'extra credits'.
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 concise, consisting of two short sentences. However, the second sentence is a direct French translation of the first, repeating the same information, which is slightly redundant but still brief and front-loaded.
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 parameterless, read-only tool with no output schema, the description is adequate. It clearly states the purpose and key data elements. It could be more complete by explaining terms like 'extra credits' or the exact period definition, but overall it provides sufficient context.
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 zero parameters, the baseline is 4. The description adds value by enumerating the output fields (quota, consumed, remaining, extra credits), which helps the agent understand what to expect in the response even without an output schema.
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 purpose: reporting current month API usage with specific data points (quota, vehicles consumed, remaining, extra credits). This is specific enough to distinguish it from sibling tools like pro_search or car_market_stats, which focus on different operations.
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 implies usage by its name and content, but does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. There is no direct guidance on when this tool is appropriate.
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.
Tools are mostly distinct, with slight overlap between pro_search and search_used_cars, but descriptions differentiate based on professional features and deal scores. Pro_deals and pro_search also have different purposes.
All tool names use snake_case with a consistent pattern: descriptive nouns for consumer tools (car_market_stats, estimate_car_price, search_used_cars) and pro_ prefix for professional tools (pro_search, pro_deals, pro_watchlist_create). No mixing of conventions.
10 tools is well-scoped for a car market API covering both consumer and professional needs. It is not too few or too many, and each tool serves a clear purpose.
The tool set covers core operations: market stats, price estimation, search, deals, watchlists, and usage. Missing a dedicated tool to retrieve full details of a single listing by ID, but agents can work around using search results.