flowforge_get_balance

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful bits beyond that: the response can be JSON or Markdown, and failures are signaled with an "Error: ..." string. It does not say whether the balance is live or cached, or whether authentication/account scoping is implicit, which is the kind of context this read tool would benefit from.

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 definition is short and front-loads the purpose in one line. The Args line adds little and the Returns line duplicates the existing output schema, but neither bloats the description meaningfully.

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 single-parameter read tool with an output schema and rich annotations, most structured burden is already carried elsewhere. What remains missing is sibling differentiation and any hint about account scoping or freshness of the balance value.

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?

Reported schema description coverage is 0% because the top-level params property carries no description, so the description has to compensate. It does note that params takes ``response_format`` only, which clarifies the nesting, but it does not restate the json/markdown tradeoff the way the enum documentation does. Adequate but thin for a zero-coverage 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?

The description gives a specific verb and resource ("Get the current account balance"), so the agent knows exactly what is fetched. It does not distinguish this from nearby siblings such as flowforge_get_usage or flowforge_get_organization, which an agent might reasonably confuse with it.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer from the name alone that this is for balance rather than usage or organization data.

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