Manage automatic DM monitoring

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

Annotations already indicate destructiveHint (deletion possible) and readOnlyHint false. Description aligns by including delete action and adds context on parameter requirements per action, but does not elaborate on further behavioral traits like rate limits or idempotency. No contradiction with annotations.

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?

Three concise sentences: first states purpose, second details start action requirements, third covers other actions. No redundant information; every sentence adds value.

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 8 parameters with conditional requirements, the description sufficiently covers all actions and their parameter needs. An output schema exists (not shown), so return value explanation is not required. Complete for the tool's complexity.

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?

With 88% schema coverage, baseline is 3. Description adds value by grouping parameters per action (e.g., start requires specific parameters) and clarifying the meaning of profile_username as 'Upload-Post profile name', which is not explicit in the schema. Enhances semantic understanding beyond the schema.

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?

Clearly states the tool controls Instagram AutoDM monitors, which is distinct from sibling tools like send_dm or reply_to_comment. Lists specific actions and resources (monitors, posts, profiles), providing a precise verb+resource description.

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?

Explicitly maps actions to required parameters (e.g., start requires post_url, reply_message, profile_username; stop/pause/resume/delete/logs require monitor_id). Provides conditional guidance for status with include_inactive. However, does not explicitly state when to prefer this tool over alternatives.

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