create_business_profile

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

No annotations are provided, so the description carries the full burden. 'Upsert' hints at idempotency, but the description does not disclose details such as what happens when the profile already exists (update all fields?), side effects, authentication requirements, or error conditions. For a creation tool, more behavioral context is needed.

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 consists of two concise sentences, each contributing meaning. The first sentence states the action and resource, and the second provides workflow context. No redundant or filler content.

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?

The tool has two parameters (one required, a complex nested object) and no output schema. The description provides workflow context but does not mention return values, response structure, or error handling. Given the complexity, the description is adequate but lacks completeness; it could, for example, state what the tool returns (e.g., profile ID) or how to interpret success.

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 coverage is 100% (both parameters have descriptions). The description adds no parameter-level information beyond what the schema provides (e.g., it does not clarify how to use the 'fields' object or the optionality of customerOrgId). With high schema coverage, the baseline is 3, and the description does not exceed it.

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 explicitly states 'Create or upsert a structured business profile for an existing organization,' which clearly identifies the action and distinguishes it from sibling tools like get_business_profile (read) and update_business_profile (update). The verb 'create/upsert' combined with the resource 'structured business profile' makes the purpose unambiguous.

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 provides clear workflow context: 'Use this first in the headless workflow: existing PAT + existing org -> create_business_profile -> generate_use_cases or trigger_full_pipeline.' This tells the agent when to use the tool, though it does not explicitly state when not to use it or give alternatives. However, the workflow guidance is strong enough.

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