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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with the concrete clarification that it 'opens nothing by itself', which is exactly the ambiguity an agent would otherwise have to resolve from the name alone. It also identifies what the return value contains (screens, buttons, fields). It does not discuss output size, freshness (the 'checked 22 Oct 2026' date hints at staleness risk), or what happens if the UI has changed.

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 outcome and the critical 'opens nothing by itself' caveat, which is the right ordering. The middle sentence is grammatically tangled ('Returns how to do it ... and opens nothing by itself'), and the API-existence sentence is closer to justification than instruction, though it does save the agent from hunting for a REST path.

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 zero-parameter, read-only guide tool with no output schema, the description covers what it returns, what it does not do, and how to act on the result. The main omission is any warning about the brittleness of UI-step instructions — the agent has no way to know whether the returned steps are evergreen or time-sensitive beyond the parenthetical check date.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly implies the arguments (which gift, which account) are supplied later through the browser tools rather than here.

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?

The description states a concrete outcome — it 'Returns how to do it in Bloomerang step by step (screens, buttons, fields)' — which correctly reframes a tool whose name ('record_received_gift') implies an action it does not perform. It does not, however, differentiate itself from same-family guide siblings like bloomerang_create_task or bloomerang_log_interaction, which presumably follow the same pattern.

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?

It gives an explicit follow-on path: use this to get the steps, then execute them with the cotlet_browser_* tools in the user's Bloomerang Cloud Browser. The third sentence explains why there is no API-based alternative for agents. It stops short of stating when NOT to use it (e.g., read-only lookups or other Bloomerang operations) but the routing guidance is clear.

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