kya_getHeaders

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

No annotations are provided, so the description carries full burden. It discloses that a 'Kya-Token' header is returned and suggests usage, but omits behavioral traits like access requirements, idempotency, or side effects. It does not state if the operation is read-only or has any destructiveness.

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 concise with two short paragraphs, front-loading the core purpose. It includes usage examples efficiently. Some minor redundancy exists, but overall it is 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?

Given no output schema, the description only mentions the return of a 'Kya-Token' header without detailing the response format. It covers usage context well but lacks completeness about the returned data structure. Complexity is low (1 param), so the gaps are moderate.

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 sole parameter 'merchant' has a helpful schema description. The tool description adds no further meaning beyond what the schema already provides. With 100% schema coverage, baseline 3 is appropriate as no extra value is added.

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 'Kya-Token' identity headers for HTTP requests, specifying the verb ('Get') and resource ('identity headers'). It distinguishes itself from the sibling 'kya_getAgentIdentity' by indicating a prerequisite call.

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 tells when to use: for attaching headers to Playwright, browser extensions, or any HTTP client. It advises calling 'kya_getAgentIdentity' first, providing a prerequisite. However, it does not explicitly mention alternatives or when to avoid using this tool.

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