reddit_account_me

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

Annotations only say readOnly/non-destructive; the description adds the non-obvious fact that this call is unmetered and never consumes a credit, plus the 402 error semantics and the presence of a top-up URL in error responses. That is behavior an agent cannot get from structured fields.

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?

Front-loaded with the core purpose and the cost caveat, and most sentences earn their place by covering the 402 workflow. Slight redundancy between 'not metered' and 'never costs a credit' costs it a point.

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?

With no output schema, the description names both return values (balance, usage totals) and supplies the error-handling context for 402. Nothing an agent needs to invoke or interpret this call is missing.

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?

Zero parameters, so there is nothing to mis-specify and the baseline is 4. The description correctly implies a no-argument call without adding noise about nonexistent inputs.

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?

States a specific resource and outcome: returns the account's remaining credit balance and usage totals. Clearly distinguishable from every sibling, which are Reddit data-fetching tools, not account/billing introspection.

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?

Explicit when-to-use guidance: call it before running something expensive, use it to check whether a planned batch fits the balance, and call it after a 402 to report remaining credit. It even explains what a 402 from another tool implies, which is the alternative signal an agent needs.

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