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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the age-window relaxation nuance ("window widens within a run only") but omits permissions, whether the scan is asynchronous, side effects, and what the call returns.

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 front-loads the purpose and then packs relevant parameter detail into a compact follow-up sentence. The second sentence is dense but contains useful semantics rather than filler.

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?

For a mutation tool with no annotations, no output schema, a nested params object, and 0% schema description coverage, the description is incomplete. It covers purpose and some nested discovery parameters but omits the required agent_id, the overall params shape, and start/return behavior.

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 0%, and the description compensates partially by listing allowed channel values and giving ranges/defaults for max_post_age_days and post_age_relax_steps. However, it leaves the required agent_id entirely undocumented and does not describe the structure of the params object beyond x/instagram discovery fields.

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 action, "Start a leads discovery scan," and enumerates supported channels. It is clear what the tool does, though it does not explicitly distinguish itself from sibling scan tools such as continue_scan or trigger_scan_schedule.

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?

There is no explicit guidance on when to use this tool versus continue_scan, trigger_scan_schedule, or create_scan_schedule. With many related scan tools, the agent is left to infer that "Start" means a new immediate scan.

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