get_synced_crypto_balance

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds scoping constraints ('single', 'by its cryptocurrency symbol') but does not disclose response format, error behavior, or case sensitivity beyond what annotations provide.

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 one sentence of 13 words, front-loaded with the action verb. Every word contributes to meaning, with no filler or redundancy.

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?

No output schema exists, so the description should clarify return value, but 'single balance' conveys the core concept. Combined with the readOnlyHint and simple two-parameter schema, the description is nearly complete; it only lacks explicit return format or not-found behavior, which are minor for a straightforward getter.

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?

Schema coverage is 100%, with both parameters (crypto_id and symbol) described in the schema. The description's phrase 'looked up by its cryptocurrency symbol' reinforces the schema but adds no new semantic detail beyond what is already documented.

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 uses a specific verb 'Get' with a clear resource 'single balance' and scoping 'inside a synced crypto account, looked up by its cryptocurrency symbol.' It distinguishes itself from sibling tools like get_crypto_synced_balance_history and get_single_synced_crypto by focusing on a single balance lookup rather than history or account details.

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 when to use the tool (to fetch a single balance by symbol) but does not explicitly state alternatives or exclusions. There is no mention of when to prefer this over balance history or refresh_synced_crypto, leaving the agent to infer the intended context.

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