pylon_create_contact

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

Without annotations, the description bears full responsibility for behavioral disclosure. 'Use carefully' hints at potential impact but fails to explain what behaviors or side effects the agent should be aware of, such as permissions, duplicate handling, or notifications.

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 minimal and front-loaded, but the second sentence ('Use carefully') adds little value. It is concise but sacrifices necessary detail.

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 lack of annotations and output schema, the description is insufficiently complete. It omits return values, side effects, and validation rules, leaving the agent with significant uncertainty about the tool's behavior.

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 only 33% (only portal_role has a description). The tool description does not elaborate on email or name, leaving the agent without guidance on format, uniqueness, or intended structure beyond the schema's type constraints.

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?

Clearly states 'Create a new customer contact in Pylon' with a specific verb and resource, distinguishing it from contact retrieval/search tools like pylon_get_contacts and pylon_search_contacts.

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 admonition 'Use carefully' is too vague and provides no context on when to use this tool instead of alternatives like pylon_get_contacts or pylon_search_contacts, nor does it mention prerequisites or restrictions.

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