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 adds behavioral detail the annotations cannot: it returns {enabled: false} when no auto reply is configured, and it discloses the fallback and AI configuration fields returned.

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?

Front-loaded with the [read] marker and the core resource statement, followed by scoping, platform enum, and a compact return shape. Dense and purposeful, though the multi-clause opening sentence packs several ideas together rather than separating them.

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?

There is no output schema, and the description supplies the return shape itself (enabled, mode enum, rules, fallback, ai), plus the empty-state behavior. Combined with the platform enum, an agent has everything needed to call and interpret this tool.

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% — the schema only has bare titles — so the description must compensate, and it does: it spells out platform as ig|wp|fb|tw|tg and explains that account_id is an account reference resolvable via list_social_accounts. Nothing about the two required params is left ambiguous.

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 and resource: read the message auto-reply settings of one account. It distinguishes itself from the near-sibling get_post_auto_reply by explicitly scoping to incoming messages/DMs rather than comments, so an agent can route without opening either schema.

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?

Gives the condition that selects the alternative explicitly (comments: get_post_auto_reply) and points to list_social_accounts for resolving the account id. It does not mention the sibling mutation tools set_account_auto_reply or test_account_auto_reply, which would complete the routing picture, but the read-vs-comments exclusion is clear.

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