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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them by stating 'no signature', which is genuine auth/execution context: it tells the agent no signed transaction is required. It stops short of return-format or pagination detail.

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?

Three short clauses, front-loaded with the core action and with the caveat about signing placed immediately after. Nothing is redundant, though the final parenthetical is compressed enough to read as a fragment.

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 should carry more of the return contract; 'full details ... including its endorsers' is suggestive but does not say what fields come back or whether the result is paginated. For a simple 2-parameter read tool whose annotations already cover safety, this is adequate but leaves a clear gap.

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 adds real meaning for `caller` — 'the account whose view to read (for caller-dependent results)' explains why the parameter exists, beyond the schema's terse 'run the query as'. `claim_id` gets no added detail, but the schema already specifies 0x-prefixed 32-byte hex.

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 ('Get full details of one Life and Work claim') and names what is included ('including its endorsers'). It is clear and distinguishable from write siblings like make_claim_* or endorse_claim, though it does not explicitly disambiguate against the adjacent readers geode_lifeandwork_get_endorsers or geode_lifeandwork_get_resume.

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?

The description never states when to choose this over geode_lifeandwork_get_endorsers or get_matching_claims, nor any prerequisites or exclusions. The only contextual hint is that `caller` yields 'caller-dependent results', which is parameter behavior, not usage routing.

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