hedera_get_account_nft_allowances

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

With no annotations, the description must fully convey behavioral traits. It indicates a read operation but does not disclose any specific behaviors like rate limits, permission requirements, or what 'active' means. It minimally states the source ('Mirror Node') but lacks detail beyond that.

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 a single, well-structured sentence of 15 words, front-loading the action ('Read'). Every word contributes essential information without redundancy or fluff.

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 no output schema and no annotations, the description covers the basic purpose and source but omits details like return format, pagination, or explanation of 'active.' It is minimally sufficient for a simple read tool but lacks completeness.

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 schema has 0% description coverage for the sole parameter accountId. The description adds meaning by implying accountId is the account whose allowances are read, but does not provide format, constraints, or examples. For a single obvious parameter, this is adequate but not exceptional.

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 explicitly states 'Read an account's active NFT (approve-for-all) allowances from the Mirror Node,' which clearly identifies the verb (Read), resource (account's NFT allowances), and source (Mirror Node). It distinguishes from sibling tools like get_account_allowances (broader) and get_nft_info (individual NFT) by specifying NFT approve-for-all allowances.

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 provides no guidance on when to use this tool versus alternatives, no exclusions, no prerequisites, and no context about when not to use it. It simply describes what it does, leaving the agent to infer when to use it.

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