partner_create

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

Annotations declare readOnlyHint=false and destructiveHint=false, aligning with 'Create' but the description adds no behavioral context beyond the action. It doesn't disclose return behavior, side effects, or idempotency issues, which are critical for a creation tool. The description fails to add value beyond annotations.

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 a single sentence that directly states the purpose and key input requirement. It is concise and front-loaded with no extraneous words.

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?

Despite simplicity, the description lacks important context: it doesn't describe the response structure (no output schema), error conditions, or validation rules. For a creation tool, this incompleteness may hinder an AI agent from using it correctly without additional assumptions.

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 schema covers all parameters with descriptions (100% coverage). The description reinforces that partnerDto should include AccountingCustomerParty, but adds minimal extra meaning. For `companyId`, the description does not mention it, relying on schema. Baseline 3 is appropriate.

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 clearly states the tool creates a new partner for a company, specifying the required input format. It distinguishes from siblings like partner_get and partner_search by the action 'Create'. However, it doesn't elaborate on what a partner is, but the purpose is sufficiently clear.

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 implies usage by stating what to provide, but it doesn't explicitly state when to use this tool versus alternatives (e.g., for adding new partners vs updating existing ones). No prerequisites or exclusions are mentioned, relying on implicit understanding.

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