scf_create_vendor

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds value beyond that by disclosing the editor+ role requirement and the meaningful side effect that the platform auto-scores risk based on criticality and data handling. These details help the agent anticipate post-creation 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?

The description is a single compact sentence that front-loads the core action, then adds the permission and side-effect context. Every clause earns its place and there is 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 description covers the core purpose, required permission, and the primary behavioral side effect, while the input schema fully documents all eight parameters. It omits explicit return-value or post-creation confirmation behavior, but given the high schema coverage and simple create semantics, this is only a minor gap.

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 documents every parameter. The description adds minimal extra meaning by connecting criticality to automatic risk scoring, but it does not elaborate on individual parameters such as status, website, or contact_email beyond what the schema provides.

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 opens with a specific verb and resource, 'Create a vendor in the TPRM registry,' and explicitly labels the operation as a write with an editor+ role. This clearly distinguishes it from list, get, update, and trigger siblings such as scf_list_vendors, scf_get_vendor, and scf_update_vendor.

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 gives clear creation context and notes the required editor+ role, implying use when a new vendor must be added. However, it does not explicitly contrast with scf_update_vendor or state that it should not be used to modify existing vendors; the alternative guidance is implied rather than stated.

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