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

No annotations are present, so the description carries the full behavioral burden. The parenthetical '(offline)' adds one useful trait by implying no network call or external lookup, but it does not disclose input requirements, failure modes, or what the generated .vcf contains.

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 only one compact clause and the offline behavior is front-loaded. It loses a point because the leading 'vCard:' label is redundant with '.vcf contact card' and the structure conveys no additional information.

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?

With one undocumented parameter, no annotations, and no explanation of what q should contain, the tool is under-specified for correct invocation. The presence of an output schema helps only when actually reading results, not when deciding how to fill q.

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 sole parameter q is undocumented in the schema (0% coverage) and the description never mentions it. An agent must infer from the tool name that q is a phone number, which is not confirmable from the description.

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 states a specific action ('Generate') and a clear artifact ('.vcf contact card), and notes the offline nature, which is enough to distinguish this from phone-related siblings like phone or phonefmt. However, it never states what input the tool consumes, leaving the mapping to the q parameter implicit from the tool name.

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?

There is no guidance on when to choose phonevcard over alternatives. With many nearby phone-formatting and phone-lookup tools, the description should at least state that this tool is for producing a contact-card file rather than validating or looking up phone data.

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