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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial context: free, keyless, no wallet or signature required, and that Vealth sends no email so this call is the only way the user learns of a status change. It also describes the state machine (pending has no packet; posted yields a workId that behaves like any other claimable packet), which is behavioral information unavailable from the schema.

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?

Front-loaded with the core action and the state outcomes, then the two call modes, then the semantics of each state. The cost/keyless/signer point is stated twice ("Free, keyless, no wallet needed" and the closing "Cost and signer: free and keyless, nothing to sign"), which is wasted space in an otherwise tight description.

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?

An output schema exists, so return values needn't be explained; the description instead covers what an agent actually needs beyond that — the state model, the claimability transition at 'posted', the absence of email notification, and the cost/signing profile. Nothing needed to call this correctly is missing.

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; the description raises it slightly by framing the two parameters as mutually exclusive modes with different output shapes (single intake vs. a list of all places for a wallet). That framing adds a little semantic value over the schema's per-field text, which already says wallet is "optional instead of intakeId."

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 — reading the status of an intake (pending/posted/rejected with reason) — and names the three result states, which an agent can match to outcomes. It does not distinguish itself from the sibling place_standing, which a reader must infer, so it falls short of the 5 bar for sibling differentiation.

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?

"Pass intakeId for one, or wallet to list every place that wallet handed over" tells the agent exactly which mode to pick for a single lookup vs. an enumeration. It also clarifies what each state means for follow-up (pending = nothing to claim, posted = claimable workId). No explicit "use X instead" exclusion against place_standing or work_status, so 4 rather than 5.

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