set_agent_contact

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

Given no annotations, the description carries the full burden. It discloses that new/changed emails trigger operator email reply verification and mentions 'Free with allowance auth', providing behavioral context about activation and authorization. However, it does not address whether the operation overwrites existing info or requires specific roles.

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 sentences (or three clauses) that front-load the purpose and include only essential details. Every sentence contributes meaning, with no redundancy.

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 setter with 3 params, no output schema, and no annotations, the description covers purpose, a key behavioral trait (email verification), and authorization/cost context. It lacks details on return value or error states, but is largely complete for the tool's simplicity.

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%, with each parameter described in the schema. The description adds only a slight rephrasing of the email parameter's effect (new/changed emails start verification), which is already in the schema. Thus, minimal added value beyond the schema.

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 verb 'Register' and the resource 'agent contact info', listing the fields (name, email, webhook). It distinguishes from sibling tools like get_agent_contact_status and verify_agent_contact_email, as it is the only setter.

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 implies usage for setting or updating contact info and mentions the side effect of email verification, but it does not explicitly state when to use this tool versus alternatives such as get_agent_contact_status (read) or verify_agent_contact_email (verification).

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