lookup_agent

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

With no annotations, the description carries full burden for behavioral disclosure. It states a lookup action but fails to mention whether it is read-only, what it returns, error handling, or any side effects. The minimal statement provides only the core action, not enough transparency.

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 a single sentence of 6 words, efficiently conveying the core purpose. It is front-loaded with the verb and noun, ideal for quick comprehension.

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 (one parameter, no output schema, no annotations), the description is too minimal. It does not specify what the tool returns (e.g., agent metadata, ID, or details), making it incomplete for an agent to decide if it is the correct tool among many similar getter siblings.

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 schema has 0% description coverage on parameters. The description adds only that the lookup is 'by wallet address', which is already implied by the parameter name 'wallet'. This adds little additional meaning beyond 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 uses a specific verb 'Lookup' and resource 'agent', clearly indicating the action and target. It distinguishes itself from siblings like 'get_agent_wallet' by specifying 'by wallet address' as the lookup method, making the purpose unambiguous.

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?

No guidance is provided on when to use this tool over alternatives such as 'get_agent_metadata' or 'get_agent_id_from_tx'. The agent must infer usage solely from the tool name and description, lacking explicit when/not or alternative suggestions.

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