manage_content

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

The description discloses important behaviors: delete is 'permanently delete' and archive moves to an archive folder. With no annotations provided, this adds meaningful context. However, it omits other behavioral details such as authentication requirements, return formats, or side effects for list actions.

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 concise and well-structured: a brief purpose statement followed by a bulleted action list. Every sentence is informative, front-loaded, and free of unnecessary 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?

For a tool with 2 parameters and no annotations or output schema, the description covers the main actions and notes the permanent delete behavior. However, it is incomplete regarding parameter dependencies (content_id needed for delete/archive) and expected outputs, and it doesn't address the overlap with list_content, making it only minimally complete.

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?

The description adds value by enumerating valid action values (list/delete/archive) and their behaviors, which the schema does not provide (no enum or property descriptions). However, it does not explicitly explain that content_id is required for delete/archive or what format it should take, leaving a gap given 0% schema coverage.

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 manages Instagram content in a specific folder and enumerates three concrete actions (list, delete, archive). However, the verb 'manage' is broad and the description does not explicitly position it against the sibling list_content tool, which likely overlaps with the list action.

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?

There is no explicit guidance on when to use manage_content versus sibling tools like list_content or manage_metadata. The action list implies usage for list/delete/archive, but the overlap with list_content for the 'list' action is unaddressed, potentially leading to confusion.

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