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

Adds significant behavioral context beyond annotations: the 7-day private reply limit, one DM per person per rule, and the distinction between private and public replies. Annotations only give safety hints (readOnly=false, destructive=false), so this description carries the burden well. It could mention rate limits or permission requirements but covers the core mechanics.

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 front-loaded with the core purpose and then flows into mechanics and targeting. It's a single dense paragraph but well-structured; every sentence earns its place by explaining behavior or targeting. Could be slightly tighter but no wasted 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?

Covers the trigger, action, network-specific behavior, and targeting parameters. With no output schema, the description doesn't explain return values, but for a creation tool that's often acceptable. It omits error handling or prerequisites like account connection status, but overall provides enough 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 coverage is 100%, so the schema already documents all parameters thoroughly. The description hints at targeting via mediaId/postId but doesn't add syntax or format details beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (Set up) and resource (Comment to DM automation), and clearly distinguishes itself from siblings like create_dm_automation or reply_to_comment by describing the trigger-action pattern. An agent can immediately tell this creates an automation rule, not a one-off message.

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?

Provides clear context for when to use this tool: setting up an automation on an Instagram account or Facebook Page. It mentions targeting behavior but does not contrast with create_dm_automation or list_comment_dm_rules explicitly. The usage scenario is implied rather than stated as 'use this instead of X'.

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