manage_metadata

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

With no annotations, the description must disclose behavioral traits but only lists actions. It does not mention side effects (e.g., whether clear is permanent), required permissions, or behavior for invalid content_id. The mention of scheduling without a corresponding action adds ambiguity.

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 with a clear list of actions. The unsupported mention of 'scheduling' is unnecessary but does not severely impact clarity.

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?

No annotations, no output schema, and minimal description leave the agent without information on return values, error handling, or side effects, especially for the destructive 'clear' action. Given the tool's 4 parameters, more context is needed.

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 has 4 params with 0% description coverage. The description maps actions to caption/hashtags, but does not explain how action interacts with other parameters (e.g., view likely ignores caption/hashtags) or the format of content_id. It adds some meaning but leaves gaps.

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 metadata for Instagram content (captions, hashtags, scheduling) and lists specific actions (update, view, clear). It distinguishes from siblings like manage_content by focusing on metadata, though the mention of scheduling is not backed by any action, which is a minor inconsistency.

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 on when to use this tool versus alternatives like manage_content or post_to_instagram. The description simply lists actions without context on when each is appropriate or any exclusions.

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