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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered; the description's restatement of 'Read-only' is redundant. What adds value is the disclosure of computed, non-obvious return contents (trust scorecards, learned playbook, today's trend brief, live metrics on published drafts) that aren't inferable from the schema.

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-loads the core action and sequencing instruction ('Call this FIRST') while the long enumeration of returned data earns its place by aiding discovery. It is dense but not padded, and the key directive is not buried.

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, so the description carries the burden of explaining the return, which it does thoroughly by listing every returned artifact. Combined with the when-to-call guidance and annotation-covered safety, only minor detail (e.g., pagination or sizing of runs/drafts) is absent.

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%, so the single influencerId parameter is fully documented in the schema itself, which even names list_influencers as the source of the id. The description adds no parameter-level detail, which is acceptable at this coverage level but yields the baseline 3.

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 (Fetch) and resource (the autonomous posting agent attached to an influencer), then enumerates its exact payload: settings, runs, drafts, scorecards, playbook, trend brief, and knowledge base. This clearly distinguishes it from the sibling get_influencer and from update_influencer_agent without requiring the 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?

Explicitly instructs 'Call this FIRST — before updating settings, deciding drafts, or answering its questions,' naming the exact conditions and the sibling operations (update_influencer_agent, decide_influencer_drafts, chat_with_influencer) that this tool should precede. Sequencing guidance leaves nothing to inference.

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