Get indexed XRC contract

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

No annotations are provided, so description must disclose behavior. It claims 'Read-only lookup' indicating safe operation, but lacks details on behavior when address not found, error handling, or any permissions needed. More transparency is expected given zero annotation coverage.

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?

One sentence with no extraneous words. Front-loaded with the key trait 'Read-only lookup.' Every word adds value.

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?

Given the tool's simplicity (1 parameter, no output schema), the description is minimally adequate but fails to describe return value or common error cases. Output schema absence means description should compensate; it does not mention what data is returned, leaving the agent with incomplete context.

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 0%, so description should add parameter meaning. However, description does not elaborate on the 'address' parameter beyond what schema provides (type, pattern). It adds no context on format examples or expected input, leaving the agent underinformed.

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?

Description clearly states 'Read-only lookup of one indexed XRC contract by address,' specifying verb (lookup), resource (XRC contract), and scope (by address). Distinguishes from sibling tools like list_xrc_contracts (listing multiple) and get_xrc_contract_events (different resource).

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?

Description implies usage for single contract lookup but does not explicitly state when to use this over siblings, nor provides exclusions or prerequisites. Usage context is implied but not spelled out.

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