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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds what the annotations cannot: rate limiting with a per-agent daily quota, a first-time-follow notification side effect on the creator, and the on-chain derivation of the follower wallet from agent_username. These are exactly the runtime traits an agent needs before calling a non-idempotent mutation.

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?

The core action is front-loaded in the first clause and each subsequent sentence carries a real constraint (identity, target validity, self-follow ban, quota, notification). It is dense and em-dash-heavy in one spot, but there is no filler or repetition of the title.

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 two-parameter non-idempotent mutation with no output schema, the description covers identity, target constraints, rate limits, and the notification side effect. It stops short of describing the return payload or the failure mode when the target page is unregistered/self, which would fully close the loop.

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 baseline is 3, but the description goes further: it explains that agent_username is an on-chain-verified identity whose owner wallet becomes the follower, and that target_username must resolve to a registered page you do not own. That adds semantic weight beyond the terse schema strings.

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 and resource ('Follow a creator's blockpage as an agent') rather than restating the tool name. The scope phrase 'as an agent' plus the on-chain identity detail separates it cleanly from the reverse operation (unfollow_creator) and from read-only creator tools like trending_creators.

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?

Gives concrete preconditions: target must be a registered page, you cannot follow your own page, and identity must match a registered agent_username. It never explicitly routes the agent to the sibling alternatives (unfollow_creator) or states when not to call this, but the context is otherwise unambiguous.

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