refresh_billing_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Force refresh' which implies a mutation or update action, but doesn't clarify if this requires specific permissions, whether it's idempotent, what side effects it has, or what the response looks like. This is inadequate for a tool that likely modifies state.

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 single, efficient sentence that front-loads the core action ('Force refresh billing status from Kinde') and adds a brief usage note. There's no wasted text, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'Force refresh' entails behaviorally (e.g., does it trigger an API call, update local cache, or something else?), what happens on success/failure, or what data is returned. For a tool with potential state changes, this leaves significant gaps.

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 input schema has 100% description coverage, with the parameter 'authToken' documented as optional. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or authentication context. Baseline 3 is appropriate since the schema handles parameter documentation.

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 action ('Force refresh') and resource ('billing status from Kinde'), and mentions a specific use case ('after plan changes'). However, it doesn't explicitly differentiate from sibling tools like 'get_kinde_billing' or 'get_subscription_status' in terms of when to use each, which prevents a perfect score.

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 ('useful after plan changes') but doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_kinde_billing' or 'get_subscription_status'. It also doesn't mention prerequisites or exclusions, leaving gaps in usage context.

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