update_company_profile

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

With no annotations, the description carries the transparency burden. It discloses a key side effect ('Regenerates an AI report used to refine CRM prospect emails') but omits mutation semantics such as whether omitted fields are overwritten, auth requirements, or response 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 tightly written sentences with no filler. The purpose, side effect, requirements, and preferences are all front-loaded.

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 7-parameter mutation tool with no output schema or annotations, the description provides the essential purpose, required fields, and side effect. However, it lacks details about successful update behavior, error handling, or partial update semantics, leaving moderate ambiguity.

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 57%, leaving website, industry, and location undocumented. The description adds useful guidance by marking name OR description as required and prioritizing name, description, and offer, but it does not clarify the remaining parameters.

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?

Description opens with 'Save/update the sender company profile,' a clear verb+resource statement. It also distinguishes itself from the sibling read tool get_company_profile.

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?

Explicitly states 'Required: name OR description' and advises preferring name, description, and offer, giving the agent actionable input guidance. It also mentions the AI report refinement context, implying use when updating profile for CRM prospect emails, though it does not explicitly contrast with alternatives.

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