create_product_feed_sftp_access

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

With no annotations, the description carries the behavioral disclosure burden. It does state the mutation ('create or replace') and the return value, which is more transparent than a bare 'Create'. However, it does not disclose consequences of replacement, such as whether existing credentials are invalidated, or any permission requirements.

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?

Two short sentences, front-loaded with the action and resource, with no filler or redundancy. Every word contributes meaning.

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?

For a simple three-parameter tool with one required field, the description provides the operation, scope ('product feed'), and output behavior ('returns credentials'). Since there is no output schema, mentioning the return value is important and is included; the only real gap is the undocumented optional ad_account_id.

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 67%, and the schema already documents feed_id and password. The description adds no parameter-level detail and does not clarify the undocumented ad_account_id, but the strong schema descriptions cover most of the parameter semantics.

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?

Description uses a specific verb-resource pair — 'Create or replace SFTP access credentials for a product feed' — and clearly distinguishes it from siblings like get_product_feed_sftp_access, activate_product_feed_sftp_access, and pause_product_feed_sftp_access. Even without the title, the resource and action are 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 context is clear: use when SFTP credentials for a product feed need to be created or replaced, and the returned credentials are meant for SFTP client configuration. It does not explicitly list exclusions or compare with get/activate/pause siblings, so it stops short of a 5.

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