flowspeech_quota

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

No annotations are provided, so the description must carry the behavioral load. "Read" correctly signals a non-mutating operation, but it says nothing about whether this call itself consumes credits, whether it requires authentication, or whether the numbers are cached/realtime — all relevant for a billing-adjacent endpoint. Adequate for a trivial zero-arg read, but not rich.

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?

One sentence, nine words, front-loaded with the verb and enumerating exactly the three values returned. No filler, no restatement of the tool name.

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 zero-parameter, no-output-schema tool this is close to sufficient — the description names the three returned quantities so the agent knows what to expect. Slightly short of 5 because units/format of the returned credits and any auth or rate-limit expectations are left unstated.

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 tool takes zero parameters, which is the baseline-4 case. The description correctly implies a global account-scoped read with no filtering knobs, consistent with the empty 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?

Specific verb ("Read") plus a precise resource ("available, remaining and reserved API credits"), including the three credit buckets returned. Nothing in the sibling list (tts, tts_multi, list_voices, get_job, new_request_id) overlaps with a credit-balance read, so an agent can route here unambiguously.

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 usage is implied by the noun "quota" — an agent would call this to check balance before or after synthesis requests — but the description never says when to call it (pre-flight check? error diagnosis? periodic polling?) or that no alternatives exist. No exclusions or triggering conditions are stated.

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