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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the mode-dependent scope (forms vs submissions), but discloses nothing about pagination, permissions, or rate limits against a remote Facebook API, leaving it at a middling level.

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 short sentences, both front-loaded with the operative condition, and zero wasted words. Every clause carries a distinct piece of information.

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?

With no output schema, the description captures the essential dual-mode behavior and the fact that results come from a connected Page/account. It omits pagination and result-shape detail, but nothing critical to invoking the tool is missing.

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 67% and notably formId has no schema description at all; the description supplies its meaning (selects submission-listing vs form-listing). accountId and profileId are already documented in the schema, so the description adds nothing there, keeping this just under full marks.

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 states a specific verb and resource ('list ... lead forms', 'list ... submissions') and clearly branches behavior on formId. It does not explicitly differentiate itself from any sibling, but no sibling in the list covers lead forms, so the risk of confusion is low.

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?

The two-sentence structure tells the agent exactly which mode to expect based on presence/absence of formId, which is the key usage decision. It stops short of naming alternatives or exclusions against other ads_* read tools, so it is not a full 5.

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