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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, so the trailing 'Read-only' is largely redundant. However, with no output schema, the description does the heavy lifting by disclosing the shape of the payload (counts per status, pending review-board cards with caption/media/target accounts), which is exactly the behavioral context an agent needs.

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 return contents and followed immediately by the usage directive. The first sentence is dense with parenthetical lists but every clause names real payload fields rather than filler.

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 and a single required parameter, the description adequately covers what comes back and when to call it. The only gap is the unresolved overlap with the sibling get_influencer, which leaves the selection decision slightly underspecified.

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 parameter is documented in the schema as 'Influencer id from list_influencers'. The description adds nothing about the parameter, so baseline 3 applies — the schema carries the parameter semantics entirely.

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 names a specific verb+resource and enumerates exactly what the read returns: personality fields, postingTargets, playbook, and draft status counts with pending review cards. It clearly separates itself from decide_influencer_drafts and update_influencer_agent, though it never explicitly distinguishes itself from the sibling get_influencer, so an agent could still hesitate between the two.

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 an explicit ordering directive ('Call this FIRST, before updating settings or deciding drafts'), which implicitly routes the agent away from update_influencer_agent and decide_influencer_drafts. There is no stated when-not-to-use condition, but the sequencing guidance is clear and actionable.

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