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

With no annotations, the description carries the full burden. It usefully discloses that data is read live from RPC (not cached/curated), which tells the agent results reflect current chain state. It does not cover failure modes (unknown account, EOA with no code), rate limits, or response shape beyond the field list.

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?

It is a single front-loaded sentence that puts the verb and resource first, then the payload. It is dense but every enumerated item is return-value information that substitutes for the missing output schema, so little is wasted; the one-sentence enumeration does hurt scanability slightly.

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 2-parameter read tool with no output schema, the description substantially covers what comes back (balance, storage, code hash/size, exported methods, NEP-330 metadata, standards, FT/NFT metadata, partner/catalog/deprecation flags), which is the main completeness risk here. Remaining gaps are error/edge-case behavior, not core capability.

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 description coverage is 100%, so both parameters are already documented, including the mainnet default for network. The description adds no syntax or format detail for account_id and no meaning for network beyond what the schema states; baseline 3 applies.

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?

Names a specific verb+resource ('What is deployed on a NEAR account, read live from RPC') and enumerates the returned fields, so the agent knows it is a full account/contract profile rather than a single-fact lookup. It doesn't explicitly distinguish itself from overlapping siblings like check_code, get_standard, or get_partner, but the breadth of the enumeration makes the scope recognizable.

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?

Usage is only implied: the enumerated payload suggests 'use this when you need a comprehensive profile of an account in one call.' There is no explicit when-to-use versus check_code/get_partner, and no stated exclusions or prerequisites (e.g., whether the account must be a deployed contract).

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