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

Annotations declare readOnly=false, destructive=false, openWorld=true, and the description usefully adds the two-phase intent workflow (prepared, not committed until signed and submitted) plus who the transaction is prepared for. That is meaningful behavioral context beyond the structured hints, though it doesn't discuss failure modes or reversibility.

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 tight sentences, front-loaded with the action and followed by the commit semantics. No filler, and both sentences earn their place.

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 still tells the agent the full lifecycle (intent prepared, then sign and submit), which is what matters for a chain-writing tool. The only gap is the required-vs-optional mismatch on the URL parameter.

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 all three parameters and the baseline is 3. The description adds no format details, and it actually mischaracterizes the link as 'optional' while url_link_to_see_more is listed as required in the schema.

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 ('Add an education claim to your Life and Work resume') and correctly scopes the content to description/keywords plus a link. It does not explicitly differentiate itself from the sibling make_claim_* variants (expertise, workhistory, gooddeed, intellectualproperty), relying on the name to carry that distinction.

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?

Clearly describes the operating context: this only prepares an unsigned intent for `signer`, and nothing takes effect until signing with geode-local-signer and submitting with geode_submit_intent. It does not, however, say when to choose an education claim over another claim type.

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