kya_reportBadgeNotPresented

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'report that you did not present' without explaining what the report does, whether it is idempotent, or any side effects. The deprecation note hints at irrelevance but does not clarify behavior.

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 extremely short—two sentences that clearly communicate deprecation and purpose. Every word earns its place, with no redundancy or fluff.

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 the tool's simplicity and no output schema, the description still fails to provide necessary context such as return values, prerequisites (e.g., need to call kya_getAgentIdentity), and how it relates to sibling tools like kya_reportBadgePresented. The deprecation note helps but does not compensate.

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 description coverage is 100%, so the input schema itself documents all parameters effectively. The tool description adds no additional meaning beyond what the schema already provides. Thus, a baseline of 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 the tool reports that the agent did NOT present a Badge at a merchant. The verb 'report' and the negation 'did NOT present' make the purpose explicit. Although the deprecation note might confuse, the core purpose remains unambiguous.

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 labels the tool as deprecated and 'no longer needed', suggesting it should not be used, but provides no guidance on when to use it if needed, or what alternatives exist (e.g., sibling tools like kya_reportBadgePresented). Prerequisites like calling kya_getAgentIdentity first are implied by the schema but not stated.

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