activate_product_feed_sftp_access

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

With no annotations, the description carries the full burden of disclosing behavior. It states the activation and resumption of ingestion, but does not mention preconditions, idempotency, side effects on already-active feeds, or whether credentials or specific permissions are required. Minimal behavioral context beyond the tool name.

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?

A single, front-loaded sentence with no filler. Every word adds meaning, and the key action and outcome are immediately clear.

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 no annotations, no output schema, and an undocumented optional parameter, the description is too sparse. It does not clarify the prerequisite relationship with create_product_feed_sftp_access, whether ad_account_id must be supplied in some contexts, or what happens if the SFTP access is already active.

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 50%: feed_id is documented as 'Product feed ID', but ad_account_id has no description. The tool description does not mention either parameter or clarify when ad_account_id is needed, so it fails to compensate for the undocumented parameter.

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 ('Activate') with a clear resource ('SFTP access for a product feed') and adds the behavioral outcome '(resume ingestion)'. This clearly distinguishes it from sibling tools like pause_product_feed_sftp_access and get_product_feed_sftp_access.

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 phrase '(resume ingestion)' implies this is used after pausing, providing some contextual guidance. However, there is no explicit statement of when to use this versus create_product_feed_sftp_access or pause_product_feed_sftp_access, nor any mention of prerequisites like the existence of SFTP access created beforehand.

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