remove_party_website_by_id

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

The description discloses atomicity, reversibility, lack of a confirm gate, idempotent retry behavior, and the exact response shapes for fresh removals versus already-removed rows. This goes well beyond the sparse annotations and gives the agent an accurate mental model of side effects.

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 sentences with no filler. The first sentence front-loads the action and the second packs the idempotency and response details efficiently.

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 there is no output schema, the description provides the response shapes for both fresh and repeated removals, explains id discovery, and confirms reversibility. An agent has everything needed to invoke and interpret the tool 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?

websiteId is richly explained as Capsule's id for the website row, discoverable from get_party where each entry carries an id. partyId's meaning is conveyed by its name and the 'party' context. The description adds useful guidance beyond the schema's partial documentation.

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 'Remove one website entry from a party by its row id' — a specific verb, resource, and unit of work. It distinguishes the tool from sibling tools like remove_party_email_address_by_id and remove_party_phone_number_by_id by targeting website entries specifically.

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 explicitly says how to discover the id via get_party and notes that the operation is reversible via add_party_website. It does not enumerate when not to use it, but the tool's role among siblings is clear.

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