Get moderation settings

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description's real contribution is the auth requirement ("Needs a PAGE token") and the blocking rule (comments containing a blocked word are hidden automatically), which goes beyond the annotations. It says nothing about what happens if settings were never configured.

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?

One front-loaded sentence that names the action, lists the returned fields, and closes with the auth prerequisite. No filler or redundant restatement of the tool name.

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 usefully enumerates the returned settings and even explains the enum values for the profanity filter (OFF, MEDIUM, STRONG), which is what an agent needs to interpret results. It stops short of covering error/default behavior or the meaning of the messaging flag's type.

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% and the single `profile` parameter is already fully documented in the schema, including the default-to-FB_PAGE_ID behavior. The description adds no additional meaning about that parameter, so the baseline 3 applies.

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?

"Read the Page's moderation settings" gives a specific verb and resource, and the parenthetical enumerates exactly which settings (blocked-word list, profanity filter level, messaging flag). The contrast with facebook_set_moderation_settings is implied by the verb "Read," so an agent can tell the pair apart.

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 verb "Read" and the PAGE-token requirement imply a safe inspection call, but the description never names facebook_set_moderation_settings as the mutation alternative or states when to prefer one over the other. Usage is inferable rather than explicit.

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