get_balance

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

With no annotations, the description carries the full burden, and it does disclose side effects, idempotency, rate limits, auth, error handling, and data privacy. However, some claims are internally inconsistent with the tool's stated function: 'All processing happens locally within the MCP server process' and 'No input data is... transmitted to external services' sit oddly beside a Stripe balance lookup, and the auth model is muddled (no auth vs. MEOK_API_KEY vs. api_key param). This keeps it from being fully trustworthy.

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 long and repetitive: the 'Behavior' section and the 'Behavioral Transparency' bullet list cover the same points (read-only, auth, rate limits, idempotency). The boilerplate 'When to use' section adds noise without value, so not every sentence 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?

The description gives useful operational details (returned balances/payouts, rate limits, error shape), but it omits the meaning of the api_key parameter and contains an irrelevant usage section. Without an output schema, the return description is thin (no structure for the 'error' objects beyond a key name), leaving the agent under-informed for correct 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?

The schema has one parameter (api_key) with no description, and schema coverage is 0%, so the description must explain it. It only mentions MEOK_API_KEY environment variable for Pro tiers and never clarifies whether/how the api_key argument should be populated; this is confusing and insufficient.

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 opening sentence states a specific verb and resource ('Get current Stripe account balance and recent payouts') and the second sentence defines the return content, so the core purpose is clear. However, the later 'When to use' text describes 'structured analysis or classification of inputs against established frameworks,' which is unrelated to balance retrieval, and no sibling differentiation is provided (e.g., vs. get_revenue_metrics).

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 'When to use' section is boilerplate that describes classification/analysis tasks, not retrieving balances, so it actively misroutes the agent. It never names or contrasts sibling tools such as get_revenue_metrics or list_invoices, and the 'When NOT to use' caveat about real-time production decisions is generic and not tied to the tool's actual capabilities.

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