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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows removal is a mutating, potentially destructive operation. The description adds no context beyond that — it does not say whether removal deletes historical data, whether it is reversible, or what happens when adding an already-tracked or private account. With annotations carrying the safety profile, this is adequate but thin.

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?

Two sentences, zero waste, with the operation set front-loaded before the usage guidance. Every clause earns its place.

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?

There is no output schema, so the description should ideally indicate what 'list' returns and what a successful add/remove yields, plus failure modes such as unknown usernames. It covers the intent but leaves the return shape and error behavior unspecified for a tool that mixes reads and destructive writes.

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 100%: the action enum and the username field (with the 'without @' and 'required for add/remove' notes) are fully documented in the schema. The description adds no format or validation detail beyond that, so the baseline 3 applies.

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 names a specific resource (Instagram accounts in the tracked workspace) and enumerates the three operations (add, remove, list), which clearly separates it from analytics siblings like get_account_stats. It does not, however, distinguish itself from the overlapping sibling list_monitored_accounts or from manage_tiktok_workspace, leaving a small ambiguity for the 'list' case.

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?

It gives explicit triggering conditions: start tracking a new account, stop tracking an account, or see all monitored accounts. That maps cleanly onto the three enum actions. It stops short of naming alternatives or exclusions, so an agent must still infer whether list_monitored_accounts is the better choice for read-only listing.

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