bulk_post_management

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

With no annotations provided, the description must disclose behavioral traits on its own, but it provides none. It does not indicate whether operations are read-only or mutating, whether archiving posts is destructive, if permissions are required, or what side effects occur. The schema reveals potential mutations (add_hashtags, update_alt_text, archive_low_performers), but the description is silent about them.

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 sentence, which is concise in length but severely under-specified for a tool with three parameters, nested objects, and four distinct actions. It is not front-loaded with the most crucial information and reads as a generic placeholder rather than a focused summary.

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 the complexity of the tool—multiple actions, nested filters, and bulk operations—and the absence of an output schema, the description is hopelessly incomplete. It provides no information about return values, side effects, or behavior for each action, leaving the agent without essential context for correct invocation.

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 only 33%, so the description must compensate, but it does not mention parameters at all. The action, filters, and bulk_operations properties are not explained in the description, leaving the agent to infer semantics solely from the schema's partial descriptions. The text adds no value beyond the schema in terms of parameter meaning.

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 states a general purpose of managing multiple posts with bulk operations and analytics, which is clear but vague. It does not specify the concrete actions (analyze performance, bulk edit, content audit, export data) available via the 'action' parameter, and 'manage' is an unspecific verb. It does imply a distinction from single-post sibling tools by using 'bulk', but lacks precision.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention suitable contexts, prerequisites, or how it differs from analytics-focused siblings like get_content_performance_report or management tools like delete_thread. There are no exclusions or alternative tool references.

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