ArcID

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine behavioral value by inventorying the returned data ('USDC settlement evidence', 'trust score'), though it says nothing about response shape, pagination, or freshness/latency of the indexer.

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 sentence with no filler; the verb+resource leads and the payload inventory follows. Every clause carries information.

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 no output schema, the description correctly compensates by listing what the record contains. With one fully documented parameter and complete safety annotations, the only remaining gap is sibling routing and any note on data staleness, which is minor for this simplicity level.

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% and the single agent_id parameter is documented in the schema as the ERC-8004 token ID in the Identity Registry. The description adds only 'for one agent', which conveys cardinality but no formatting or lookup semantics beyond the schema, so the 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?

The description gives a specific verb/resource ('Full ArcID record for one agent') and enumerates the payload (profile, owner, wallet, reputation, validations, trust score, settlement evidence). This implicitly distinguishes it from narrower siblings like get_agent_feedback and get_agent_validations by signalling a complete record, but it never names those alternatives explicitly.

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 tool takes one agent_id and returns that agent's full record, so an agent can infer it is the lookup-by-ID entry point. There is no statement of when to prefer it over search_agents (discovery) or the focused feedback/validations tools, and no prerequisites are mentioned.

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

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description still adds genuine value by disclosing the return shape: entries are classified (receipt, rating, metric, self, revoked) with a normalised 0-100 rating, and results are ordered newest first.

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?

Two tightly written sentences with zero filler; the resource and ordering are front-loaded and the second sentence delivers the return-value classification. Every clause earns its place.

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 no output schema, the description carries the burden of describing returns and does so reasonably (classification categories, normalised rating). Pagination is left entirely to the schema, which documents page/limit adequately, so nothing critical is missing for correct invocation.

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 agent_id, page, and limit are already documented in the input schema. The description adds only the implicit ordering ('newest first'), which mildly extends the schema's pagination semantics but does not clarify the parameter formats themselves.

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 and resource ('Feedback left for an agent in the ERC-8004 Reputation Registry') and adds ordering ('newest first'). It is naturally distinct from the sibling get_agent_validations, though it does not explicitly name or contrast with any sibling.

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: it is a read-only getter that returns feedback for a given agent, so an agent can infer when to call it. There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_agent or get_agent_validations.

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds the 'latest 100' result cap, but says nothing about ordering semantics beyond 'latest', pagination past 100, or behavior when an agent has no validations.

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 tight sentence with zero filler, front-loading the result count and the resource. Nothing needs to be trimmed or moved.

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 no output schema, the description should characterize the return, and it does: validation requests and responses, capped at the latest 100, from a named registry. Only the pagination/ordering edge case is left implicit, which is a minor gap for a one-parameter read tool.

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 coverage is 100% and the single agent_id parameter is fully documented in the schema, including its ERC-8004 Identity Registry token ID meaning. The description adds no format or semantic detail beyond what the schema provides, so the 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?

States a specific resource (validation requests and responses) scoped to an agent and names the source registry (ERC-8004 Validation Registry), which distinguishes it from siblings like get_agent_feedback. It is clear what the tool returns, though it doesn't explicitly contrast itself with those siblings.

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 says what is returned but gives no when-to-use guidance, prerequisites, or alternatives. An agent must infer on its own whether to call this versus get_agent_feedback or get_agent.

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

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that the tool quantifies lag magnitude, implying a diagnostic read, but says nothing about response shape, units (blocks/time), or thresholds for 'healthy'. Some added value, not rich.

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?

Two short sentences, the measurement is front-loaded and the usage cue follows immediately. No filler or restatement of the title.

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 no parameters and no output schema, the description carries a light burden: what the tool measures and when to reach for it, both of which are present. It could note the units or that a healthy result is near-zero, but the omission is minor for a zero-arg diagnostic.

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 are no parameter semantics to document. Baseline 4 applies; the description does not need to compensate for anything in the 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?

The description names a precise quantity — the lag between the ArcID indexer and the Arc chain head — so an agent knows exactly what this tool measures. It lacks an explicit verb (e.g. 'report' or 'return'), but the resource and scope are unambiguous. No sibling tool is health-related, so differentiation is not a concern.

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?

'Check this when results look empty or stale' gives a concrete triggering condition rather than generic advice. There are no when-not clauses or named alternatives, but none of the sibling tools (search_agents, get_agent, get_registry_stats) overlap enough to require routing guidance.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds real content by disclosing which aggregate dimensions exist, but says nothing about index freshness/staleness or the shape of the totals, which matters for a stats endpoint.

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 sentence that packs the resource and the full metric list with no filler. Nothing is wasted and nothing is 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 no output schema, the description carries the burden of describing returns, and enumerating the five counted categories fills most of that gap. It stops short of stating the response structure or units beyond USDC, but for a no-argument stats call it is nearly complete.

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?

Zero parameters, so the baseline is 4 per the rubric. The description correctly indicates this tool takes no filtering input — the totals are unconditional — which is the only parameter-level fact available.

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 names the specific resource (the ArcID index) and enumerates exactly what aggregates it returns: agents, owners, feedback, validations and settled USDC. That distinguishes it clearly from siblings like get_agent_feedback or get_indexer_health, which return per-entity data or operational health.

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 enumeration of registry-wide totals suggests an overview/dashboard role, but there is no explicit when-to-use statement, no mention of when to prefer it over search_agents or get_indexer_health, and no prerequisites. For a zero-parameter summary tool, implied usage is acceptable but leaves a gap.

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

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds that the source is an on-chain registry (ERC-8004), but says nothing about pagination limits, default readable_only behavior effects, or result shape.

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?

Two sentences, front-loaded with the verb and resource, then the capability set. No filler or repetition of the title.

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 read-only search tool with no output schema and full schema coverage, the essentials are present. Return shape and pagination interaction are not described, but an agent can call this correctly from the given 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?

Schema coverage is 100% so the baseline is 3, but the description earns extra: it expands the opaque enum values 'score', 'feedback' and 'settled' into 'trust score, feedback count or settled USDC', and clarifies that full-text applies to names and descriptions.

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 (Search) and resource (ArcID directory of AI agents registered on Arc, ERC-8004), and enumerates the search modes. It is clearly a discovery/browse tool, distinguishable from the get_agent sibling, but never names siblings explicitly, so sibling routing is left implicit.

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 lists capabilities (full-text, owner filtering, sorting) which implies when the tool applies, but gives no explicit when-to-use guidance versus get_agent or when-not to use it, and no prerequisites. Usage is inferable rather than stated.

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