Link a subscription to a target resource like a site or device by passing the subscription UUID and a JSON request body.
Associate a subscription with a target resource (e.g. site or device).
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| subscription_uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must carry the full burden. It only states the basic action without disclosing behavioral traits such as error handling, idempotency, permissions required, rate limits, or side effects. The agent lacks critical context.
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 immediately conveys the core purpose. It is front-loaded with the action and resource, 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?
Given the complexity (2 parameters, one a nested object) and absence of annotations or output schema, the description is insufficient. It does not specify the response format, the expected body schema, or any contextual hints about successful creation or error cases.
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 50% (the 'body' parameter has a schema description, but 'subscription_uuid' does not). The tool description adds minimal value by stating 'e.g. site or device' for the target resource, but does not explain the structure of the body or the role of subscription_uuid. It is adequate but not helpful.
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 action ('Associate') and the objects involved ('subscription' and 'target resource'), with an example (site or device). It distinguishes this create operation from sibling tools like sdcloud_list_subscription_associations.
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?
No guidance is provided on when to use this tool versus alternatives, prerequisites, or conditions. The description does not mention when not to use it or any context that would help the agent decide between this and other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.