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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the payload contents (six supported chains, five assets, capability flags), which matters because there is no output schema. It stops short of noting error modes or staleness of the status data.

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?

Three sentences, each earning its place: what it returns, the exact contents, and the intended use. Front-loaded with the verb+resource and no filler or restatement of the name.

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 zero-parameter, read-only status probe with annotations covering the safety hints and no output schema, the description carries the necessary burden by enumerating return contents and the intended pre-quote use. An agent can call this correctly without further information.

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 tool takes zero parameters, so there is no parameter semantics to describe; baseline for a no-arg tool is 4. Nothing in the description misleads about inputs, and 'confirm before requesting quotes' correctly signals that the call is argument-free and cheap.

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?

States a specific verb (Get) and resource (NEAR Protocol chain-abstraction integration status), and enumerates the returned data (chains, assets, capability flags). This is distinguishable from the other NEAR-prefixed siblings (near_quote, near_intent, near_intent_status), which concern quoting and intent flows rather than integration availability.

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 gives the triggering condition: 'Use this to confirm cross-chain settlement is available before requesting quotes.' That pins down when to call it and implies the sequencing relative to quote requests, though it doesn't name the sibling tool (near_quote) directly or state when the tool is unnecessary.

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