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

No annotations are provided, so the description carries the full disclosure burden and largely fails it. The word "existence" weakly hints that a nonexistent agentId returns a status rather than throwing, which is useful, but there is no statement about read-only safety, permission requirements, cross-chain behavior, or what the response actually looks like. For a lookup with three enumerated chains and no output schema, this is a substantive gap.

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?

A single front-loaded clause with no filler; the em-dash list of returned fields is efficient. It is telegraphic to the point of under-specification, but nothing is wasted or buried.

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?

With only two parameters the tool is simple, and the description does gesture at return values (tokenURI, metadata, existence), which matters because there is no output schema. Still, with zero annotations and no output schema, an agent lacks the behavioral and structural context needed to call this confidently instead of a sibling.

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% — both agentId and the chain enum with its default ("bsc") and its Sepolia exclusion are already documented in the schema. The description adds no parameter-level meaning beyond that. Baseline 3 applies since the schema does all the work.

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 states a specific verb and resource ("Get agent details") and names three returned fields (tokenURI, metadata, existence), so the intent is discernible. However, it gives no basis for distinguishing this tool from close siblings such as actora_identity_exists, actora_identity_metadata, actora_identity_list, and actora_identity_list_all, which appear to cover overlapping ground. An agent reading all four descriptions would have to guess which to call.

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 when-to-use guidance, no prerequisite (e.g., the agent must be registered), and no mention of the alternative tools that would be preferred for a pure existence check or a metadata-only read. Usage must be inferred entirely from the name and the one-line gloss.

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