Create contact

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile exists elsewhere. The description adds no behavioral context whatsoever - nothing about naming collisions, overwrite behavior implied by idempotency, or remote-server interaction despite openWorldHint=true.

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?

It is short, but the brevity is under-specification rather than conciseness - a single tautological sentence with no front-loaded useful content. Not verbose, but earns nothing.

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?

A mutation tool with 3 undocumented parameters, no output schema, and 0% schema coverage needs a description that compensates; this one supplies nothing. An agent has no basis for constructing address_book_url or vcard_data correctly.

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 0% across 3 parameters (address_book_url, vcard_data, filename), so the description carries the full burden and completely fails it. It names no parameter, gives no format for vcard_data (raw vCard string? base64?), and no hint that filename is an optional override.

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 restates the tool name and title ('create_contact operation') without adding any specificity about what a contact is in this system or where it lands. Only the tool name itself conveys verb+resource; the sentence contributes nothing an agent couldn't infer from 'nextcloud_create_contact'.

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 indication of when to use this versus siblings like nextcloud_create_share, nextcloud_create_calendar_event, or nextcloud_list_address_books. No prerequisites (does the address book need to exist? does list_address_books need calling first?) are stated.

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