get_usage

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

No annotations provided, so description carries full burden. It discloses that the tool consumes no quota, implying no side effects or destructive behavior. Could be improved with an explicit 'read-only' statement, but current disclosure is sufficient for a safe status check.

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?

Two sentences, front-loaded with key information. First sentence defines scope, second sentence provides usage context and a safety note. No wasted words.

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 no-parameter tool, the description comprehensively details returned data (usage, limits, slots) and usage guidelines. It is complete enough without an output schema, and sibling tools are sufficiently differentiated.

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?

Input schema has zero parameters (baseline 4). Description adds meaning by explaining the tool's output, but there is no parameter-related information needed. The description fully covers what the tool does without parameters.

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 tool's purpose: checking Svmmon account usage and limits, including subscription tier, monthly slideshows used vs cap, reset time, and per-TikTok-account draft slots. It distinguishes from siblings (e.g., generate_slideshow, list_slideshows) by focusing on usage/status rather than content creation or retrieval.

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?

Explicitly provides when to use: answering specific questions ('how many slideshows do I have left', 'check my usage') and before batch generations to confirm quota and slot headroom. Also states it consumes no quota, guiding appropriate invocation.

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