List A2A Agents

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

Annotations already declare the operation as read-only, idempotent, and non-destructive, which covers the safety profile. The description adds the 'all registered' scope but does not provide additional behavioral details such as response format, pagination, or ordering. This is acceptable given the strong annotation coverage, but the description contributes minimal extra context.

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, front-loaded sentence that directly states the action and subject with no wasted words. It is highly concise and well-structured.

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?

For a simple, parameterless list operation, the description is sufficient. It does not elaborate on return value structure, but no output schema exists and the tool is straightforward. A slight gap is the lack of differentiation from other list tools, but this is not critical for basic understanding.

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, and the schema has 100% coverage since there are no properties. The description's 'all' implies no filtering, aligning with the empty parameter set. This matches the baseline expectation for a parameterless tool.

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 specifies the action ('List') and the resource ('A2A agents'), and the phrase 'all registered' indicates the scope. It distinguishes itself from sibling tools like 'lyzr_list_agents' by explicitly targeting A2A 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?

No explicit guidance is given on when to use this tool versus alternatives like 'lyzr_list_agents' or 'lyzr_list_org_agents'. The A2A in the name implies a distinction, but the description does not articulate the appropriate context or exclusions.

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