portfolioDomainAssociate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the mutation ('Assign') and the 200-domain cap, but does not mention whether the operation overwrites existing assignments, whether it is reversible, what permissions are required, or what the response contains. The external API reference link is a pointer, not a substitute for in-description transparency.

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, front-loaded sentence with no redundant filler. Every token adds meaning: the verb, the target resource, the count limit, and the external reference. It is appropriately compact for the tool's two-parameter surface.

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 the simple two-parameter schema, the description is functionally sufficient for basic invocation. However, it does not disclose return values, failure modes, or behavioral edge cases (e.g., invalid portfolio names), and with no output schema or annotations, this leaves notable gaps for an agent relying solely on the description.

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 100%, so the schema already explains both required parameters. The description adds only the 'up to 200' context, which is also repeated in the domains parameter description. This meets the baseline, but the description does not significantly enrich parameter understanding beyond the schema.

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 uses a specific verb ('Assign') with clear objects ('up to 200 domains to a portfolio'), making the operation unambiguous. It also inherently distinguishes this from sibling tools like contactDomainAssociate (assigns contacts) or portfolioAdd (creates a portfolio). The 200-domain limit adds useful operational specificity.

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 no guidance on when to choose this tool over alternatives, when not to use it, or what prerequisites exist (e.g., whether the portfolio must already exist). It states the action but leaves usage context entirely to the agent's inference.

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