Pictory Integrations

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

With no annotations, the description carries the full burden. It discloses state-changing behavior through action verbs like 'Cancel', 'Delete', 'Disconnect', 'Authorize', 'Connect', and 'Remove', and labels clean_job as affecting 'stuck/failed' jobs. However, it does not disclose consequences, reversibility, permissions, or side effects beyond the surface action, so transparency is partial.

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 starts with a one-sentence overview and then uses a clean bullet list where each action has an inline command snippet and a short gloss. It is long, but the length is warranted by the 14 actions. No wordy filler is present, though a legend for parameter usage would be more efficient than repeated endpoint notation.

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 complex multi-action dispatcher with 6 parameters and no annotation coverage, the description is incomplete. It fails to specify which parameters are required for each action, what connection_payload should contain, the valid values for action, or how list actions use pagination. The output schema's existence doesn't compensate for missing operation-to-parameter mapping, so an agent cannot reliably construct valid requests.

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 0%, so the description must compensate. It lists action names and endpoints including {id} placeholders, implying job_id and connection_id usage, but it never explicitly maps schema fields (action, page, page_size, connection_payload, job_id, connection_id) to actions. The connection_payload parameter is not mentioned at all, and page/page_size are undocumented.

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 tool's domain ('Manage third-party cloud integrations, account quotas, AI credits, and job cleanup') and enumerates 14 specific actions with endpoints and one-line behaviors. It distinguishes itself from siblings like pictory_video and pictory_transcribe through its focus on integrations, quotas, credits, and jobs. The verb 'Manage' is broad, but the action list provides concrete 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?

Usage is implied through each action's description (e.g., 'Cancel or delete a stuck/failed job' tells when clean_job is appropriate), but there is no explicit guidance on when to use this tool vs. sibling tools like pictory_video or pictory_projects. No exclusions or alternatives are named, leaving tool selection to inference from the action list.

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