Get A2A Agent Card

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by revealing the content of the response (card URL and skill list) and the broader purpose of the server (connecting agents to the consultation desk). It does not contradict annotations and provides context beyond the structured fields, such as the note that property sale is handled by a licensed real-estate agent. This adds useful behavioral nuance for an agent deciding whether to invoke this tool.

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 front-loaded with the core purpose: it returns the A2A Agent Card URL and skill list. It then elaborates on the server's skills and use cases, which is relevant context. While it is bilingual and somewhat verbose, the repetition serves a clear audience and every sentence contributes to understanding the tool's role in agent-to-agent discovery. It could be trimmed slightly, but it is well-structured and not wasteful.

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 tool is simple (no params, read-only, no complex logic). The description covers what it does, when to use it, and what it returns (card URL and skill list). It also provides domain context about the server's purpose, which helps an agent understand the tool's place in the broader system. Given the low complexity and the presence of an output schema (which handles return format), the description is complete and sufficient.

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 has zero parameters, so there is nothing to explain. The description goes beyond by specifying what the tool returns (card URL and skill list), which effectively conveys the output semantics. With 100% schema coverage (no params), the baseline is 4, and the description's clarity about the output justifies a higher score.

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 returns the A2A Agent Card URL and list of published skills for the server. It uses a specific verb ('returns') and names the resource (A2A Agent Card), and it is clearly distinct from sibling tools that focus on cost categories, auditing, or price verification. The mention of use cases for external A2A agents further clarifies the purpose.

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 explicitly says 'Use when an external A2A-capable agent wants to discover and connect.' This gives clear context for when to use the tool. It also lists the specific skills (construction estimate integrity audit, verified fair price proof, Japan property acquisition + renovation intake) that are discoverable via the card, helping the agent decide if this is the right entry point. While it doesn't explicitly mention alternatives or when not to use it, the sibling tools are clearly direct MCP tools, so the distinction is implied.

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