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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context: accounts absent from this list cannot be targeted until the user connects them in the app. It does not discuss any caching or freshness of the returned account list, which is the one remaining behavioral unknown for a read tool.

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, front-loaded with the purpose before moving to ordering and the project constraint; each sentence earns its place. The final sentence is somewhat dense, packing the project-scoping rule and the id-vs-platform-name preference together, which slightly hurts scannability.

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 carries the burden of explaining what comes back, and it does so by naming id, platform and handle plus the per-account `project` field. For a zero-parameter read tool, an agent has everything it needs to call it correctly and interpret the result.

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 no parameters, so there is no parameter semantics to elaborate and the baseline applies. The description usefully spends its space on the implicit contract with downstream tools instead of restating a 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?

The description opens with a specific verb and resource ("Lists the social accounts connected to Broadcast") and even names the returned fields (id, platform, handle). It distinguishes itself from the sibling tools by positioning itself as the prerequisite that schedule_post, validate_post and update_post depend on.

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?

It gives explicit ordering guidance ("Call it first") and names the concrete downstream tools that consume the ids, which is exactly the when-to-use signal an agent needs. It also states the consequence of a missing network, so the agent knows when this call is required rather than optional.

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