tokportal_get_credit_costs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no behavioral details beyond what annotations provide, such as what pricing data is returned (base costs, tiers?) or if external API calls are made. This is adequate but not additive.

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?

Extremely concise at 3 words. While it's slightly under-informative for a tool in a large API surface, it does not waste words. A front-loaded one-liner is acceptable for a simple zero-param query.

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?

Given the complexity of the sibling set (many credit/billing related tools), a 'Get credit pricing' description is too sparse. There is no output schema to explain return values, and no clarification on what pricing scope or structure is returned. For a simple zero-param tool, this is minimally complete but lacks helpful 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 0 parameters and 100% schema description coverage, there is nothing missing from the schema. The description does not need to add parameter meaning. Baseline 3 is appropriate.

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 'Get credit pricing' is largely a tautology of the tool name and title. It states what the tool does (retrieve pricing) but gives no detail about what kind of credit pricing (e.g., per-segment, per-platform, bulk discounts?), which is needed given the large set of sibling tools.

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 on when to use this tool vs alternatives like tokportal_get_credit_balance or tokportal_list_credit_transactions. The context of pricing discovery is implied, but there is no mention of prerequisites or scenarios where other credit-related tools would be more appropriate.

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