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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description goes beyond them with genuinely additive facts: analysis runs asynchronously in the background, it consumes the plan's AI image allowance, and it returns a job id to poll. It stops short of stating what happens on re-invocation or partial-failure behavior, so a 4 rather than a 5.

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 dense sentences with the primary action front-loaded and the cost/polling caveats subordinated in parentheses. The nested "for the persona cover" clause is a slight readability stumble but no sentence is wasted.

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 correctly supplies the return contract (job id) and the polling path, and annotations cover the safety profile. It is nearly complete; only edge cases like re-running the same persona or failure states are unaddressed, which is low-risk for an async job-start 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 description coverage is 100%, so the schema already documents every parameter including the platform/source_kind pairing and the required-for-each-mode notes. The description adds platform-to-mode mapping but nothing about name or identifier limits beyond what the schema already says, so the baseline 3 applies.

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+resource ("Start learning a writing persona from recent posts") and immediately disambiguates the two operating modes (connected_account vs public_profile) with their platform sets. An agent can distinguish this from siblings like generate_persona_post or delete_persona without opening 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 maps source_kind to allowed platforms (connected_account: instagram/twitter/youtube; public_profile: youtube/medium/mastodon/bluesky), which is the key selection decision, and names the follow-up tool (get_persona_job_status) for polling. Routing is fully specified rather than inferred.

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