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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered elsewhere. The description adds the scoping fact that results are per-account publishing destinations, but says nothing about return shape, pagination, or what happens when an account has no destinations.

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, front-loaded with the action and resource, and the follow-up sentence justifies why the tool matters rather than repeating the name. Slightly indirect phrasing ('this is where the id for those comes from') costs a point.

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 one-parameter read tool with no output schema, the description explains intent and downstream use but never describes what the returned destinations look like (ids, names, types, ordering). An agent knows why to call it but not what to expect back.

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?

Only one parameter with 100% schema description coverage, so the schema already explains accountId fully. The description reinforces that the listing is scoped to a single connected account but adds no format or sourcing detail beyond the schema.

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?

Specific verb (lists) plus the actual resource (pages, organizations, boards a given account can publish to), which fixes the misleading tool name 'list_subaccounts'. It does not explicitly distinguish itself from near siblings like list_accounts or choose_facebook_page, so it stops short of a 5.

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 second sentence implies the usage context (you need this to obtain a page/company id before publishing to Facebook or LinkedIn), which is genuinely helpful. But there is no explicit when-not-to-use and no named alternative such as list_accounts or choose_facebook_page, which sits among the siblings and could plausibly be confused with this tool.

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