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

Annotations already cover read-only, idempotent, non-destructive, and closed-world. The description adds genuinely new behavioral context: an approved AlertForge account connection is required, OAuth clients must run the authorization flow and only ask the user to sign in and approve, plus a setup URL. The per-scene cap of 4 effects is a useful domain constraint not expressible in 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 sentences, each carrying content: auth prerequisite, OAuth client behavior, purpose. The purpose statement is placed last behind auth boilerplate rather than front-loaded, which is a minor structural weakness for a reader scanning for what the tool does.

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 parameters, no output schema, and full annotation coverage, the description covers the gating prerequisites and the scope of results. It does not describe the shape of returned items (e.g., effect IDs vs display names), which would help an agent chain into a create call, but that is a small gap.

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?

The tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level value is added or needed.

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 final sentence gives a specific verb and resource ('List the particle overlay effects') and adds a constraint ('that can be Color-Dodge-blended onto a scene, max 4 per scene'). It is distinct from sibling list tools like list_scene_kinds or list_overlay_projects by naming the exact resource, though it never explicitly contrasts itself with them.

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?

Usage is implied: call this to discover which particle effects are blendable onto a scene before compositing. There is no explicit when-not guidance and no named alternative among the many sibling list/create tools, so the agent must infer selection.

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