kya_getAgentIdentity

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

With no annotations, the description carries full burden and explains key behaviors: it is a read-only identity declaration ('No card is issued. No money moves'), how merchants may challenge, and the response includes agent_disclosure text. Missing idempotency details, but otherwise thorough.

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 informative but verbose, including marketing-like phrases ('Prove it before you shop') and repetition. It could be more concise while retaining key info, so a score of 3 reflects moderate conciseness.

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?

No output schema exists, yet the description only partially explains return values (mentions agent_disclosure text). It lacks details on error responses, status codes, or what happens on failure, leaving gaps for a tool critical to shopping flow.

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 coverage is 100% and both parameters have clear descriptions. The description adds context about the merchant parameter ('The merchant or website the agent intends to visit') but does not add meaning beyond the schema, so baseline 3 is appropriate.

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 what the tool does: it declares the agent's identity to merchants before shopping, distinguishing it from siblings like kya_getCard (payment). It uses specific verb+resource: 'declare identity' and explicitly says 'Call this BEFORE any shopping action'.

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 provides explicit when-to-use guidance: 'Call this BEFORE any shopping action — browsing, searching, or buying.' It also tells the agent what to do when challenged and mentions alternative kya_getCard for payment, fulfilling the guidelines dimension fully.

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