Get one Ripar agent

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

Annotations already declare readOnlyHint=true, but the description adds valuable insight about the 'not found' behavior: returns found:false with reason, and the literal 0 representation. This goes beyond annotations and correctly explains absence is not an error.

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 two sentences, front-loaded with the main purpose and immediately followed by a crucial edge-case explanation. No unnecessary words or redundancy.

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?

The description covers the core fetch behavior and not-found semantics, but leaves ambiguity about optional identifier precedence (e.g., if multiple identifiers are passed) and response shape affected by includeJobs/includeReputation. Still, schema descriptions fill some gaps.

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% with descriptive text for each parameter. The description references id/domain/address but does not add new parameter-level meaning beyond schema descriptions. 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 clearly states the tool fetches a single agent record from the IdentityRegistry by id, domain, or Algorand address. The verb 'Fetch' combined with 'single' distinguishes it from sibling search tool ripar_search_agents.

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 indicates usage for retrieving one specific agent via unique identifiers, contrasting with search. It does not explicitly name alternatives or state when not to use, but the context is clear enough for selection.

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