create_contact_field_tab

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

With no annotations, the description must disclose behavior. It only lists parameters and constraints; it does not mention write effects, permissions, error cases, or return values. The insert_after parameter implies ordering, but the tool's broader behavioral profile is unaddressed.

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?

Concise, front-loaded with a clear purpose, followed by a compact argument list. No redundant or non-informative text.

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 create operation, the description is adequate but incomplete. It lacks information about return values, conflicts, or permissions. The presence of an output schema helps, but the description does not reference or summarize it.

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 schema has no descriptions (coverage 0%), so the description's parameter details are essential. It provides character limits, allowed contact types, and optional insert_after semantics, adding meaning beyond the raw 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 tool creates a new contact fields tab, with a specific verb and resource. It distinguishes from sibling tools like create_contact_field by focusing on tabs, but does not explicitly contrast with other tab/group creation tools.

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?

No guidance on when to use this tool versus alternatives like create_contact_field_group or create_contact_field. The description only defines the action without contextual usage cues or exclusions.

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