check_account_block

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

Discloses read-only HTTPS behavior, required token (MCP_FNS_CALC_TOKEN), and that it returns an object or error. No annotations present, so description carries full burden and does so well.

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 purpose, then uses bullet points for usage, side effects, and return value. Every sentence adds value, 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?

Given output schema exists, description explains return structure ({suspended, inn, details, disclaimer}) and covers prerequisites, limitations, and side effects comprehensively.

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 has 100% coverage for 'inn' parameter with description; tool description adds context like '10–12 digit' and 'from FNS', enhancing meaning beyond 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?

Clearly states it checks bank account operation suspension info from FNS using a 10–12 digit INN. Differentiates from sibling tools like check_tax_arrears and check_ip_status.

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 specifies when to use (treasury/compliance check before large outbound payment) and when not to use (real-time bank balance, offline unavailable).

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