add_challenger

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

With no annotations, the description carries the full burden and uses it well: it discloses the side effect that enabling the first challenger opts the config into Proof-Me, and it explains channel-specific enrollment behavior (telegram captures chat_id later; whatsapp must pre-declare phone). It stops short of describing return values or failure modes, so not a 5.

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 organized into purpose, behavioral detail, agent workflow, and access notes, and every sentence adds information. It is slightly longer than strictly necessary, but front-loaded and free of 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 no annotations and no output schema, the description still covers the main behavioral side effects, the required access setup, and the immediate next step. It is missing only minor operational details such as return value/error behavior, so it is strong but not fully complete.

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%, so baseline is 3, but the description adds real meaning beyond the schema: it explains when whatsapp_phone is required and how channel changes enrollment behavior. This compensates and justifies a 4.

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?

Description opens with a specific verb and resource: 'Pre-enroll a Proof-Me challenger (a trusted contact) on a HITL config.' It also distinguishes the tool's role from its sibling invite_challenger by describing the enrollment-link step as a separate follow-up, making the purpose 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?

Gives explicit sequencing ('After adding a challenger, call invite_challenger') and an explicit when-not ('start_login does NOT open this tool'), plus a clear access prerequisite. It does not explicitly contrast with remove_challenger/list_challengers, but the workflow guidance is strong enough to place it above a bare context statement.

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