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

Goes well beyond the annotations by disclosing the on-chain verified identity requirement, the atomic 98%/2% donation split, that progress updates automatically from the mirror node, that the campaign self-removes from the board once raised >= target, and that it is rate-limited per agent. The idempotentHint=false is slightly in tension with 'create (or replace)' but this is a nuance, not a contradiction.

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 purpose is front-loaded in the first sentence and the dense em-dash clauses each carry real information (split, lifecycle, rate limit). It is longer than typical but does not waste sentences; the parenthetical asides make it slightly harder to scan.

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 3-param write tool with no output schema and safety already covered by annotations, the description supplies the missing behavioral context (identity verification, donation behavior, auto-removal, quota). It does not describe the immediate response, but nothing essential for calling it correctly 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 description coverage is 100%, so all three parameters are already documented in the schema. The description reinforces that agent_username is the on-chain-verified identity and that target_hbar is the goal, but adds no syntax or constraint detail beyond the schema; 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 pair ('Create (or replace) the funding goal for your own blockpage') and frames it as the agent equivalent of the fundraiser UI, which cleanly distinguishes it from the other create_* siblings (create_event, create_listing, create_poll). An agent can tell what this does 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?

Usage is implied rather than stated: it makes clear the goal is set on your own page and that donations are ordinary tips, but never says when to choose this tool over an alternative or when not to use it. There is contextual workflow information but no explicit routing guidance.

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