import_agent

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

With no annotations, description fully discloses behavior: read-only operation (nothing written to DB), fetches /.well-known/agent-card.json, returns preview and missing fields. No hidden side effects.

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?

Description is concise: 4 sentences with a bullet list for return fields. Front-loaded with action verb 'Pre-populate'. Every sentence adds value without repetition.

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?

Despite no output schema, description details return fields (source_url, preview, missing_fields, note). Given low complexity (one param) and clear purpose, description is complete for agent to use correctly.

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 has one parameter 'domain_url' with 0% description coverage. Description adds meaning by explaining it's the domain to fetch from, giving examples ('https://example.com' or 'example.com'). Fully compensates for missing schema 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?

Description clearly states the tool's purpose: pre-populate an Aidress registration from a domain's A2A agent card. It specifies the action (fetch and map) and the resource (agent card from well-known URL), distinguishing it from sibling register_agent.

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?

Explicitly states when to use this tool: to preview before calling register_agent. Tells the agent that nothing is written to DB and to review preview, fill missing fields, then call register_agent. Provides clear alternative.

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