Create vCard

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

The description discloses that vCards are immutable and require deletion for changes, which is a key behavioral trait beyond the annotations. Annotations already indicate readOnlyHint=false, but the immutability detail adds context about post-creation 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?

Two short sentences, no wasted words. The first sentence states purpose, the second adds a critical behavioral note. Very efficient.

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 complexity (14 parameters, nested objects, no output schema), the description is minimal. It does not explain the campaign context, return values, or error handling. Adequate but not rich.

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 tool description does not add any parameter-specific information beyond the input schema. Schema description coverage is 57%, so the schema partially documents parameters, but the description provides no additional meaning. Baseline score 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 'Creates a virtual business card in a campaign.' It uses a specific verb and resource, distinguishing it from sibling tools like create_ad_group or create_text_campaign. The mention of immutability adds further clarity.

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 when to use this tool (to create a vCard) and notes immutability (delete and recreate to change), but does not explicitly state when not to use it or compare to alternatives like delete_vcards or update functions. Usage guidance is implied rather than explicit.

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