lemma_get_entity_lockbox

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

With no annotations, the description carries the burden of signaling behavior. The verb 'Get' clearly indicates a read-only operation, and the parenthetical adds useful domain context. However, it does not mention response shape, null/absence behavior, permissions, or side effects.

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 description is a single sentence that leads with the verb and resource, and the parenthetical explains the domain term without added fluff. Every part earns its 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?

For a simple one-parameter read-only getter, the description sufficiently conveys what is returned and for whom. Minor gaps such as null handling or the exact address field format are not disclosed, but the tool's low complexity makes the description largely complete.

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 schema has 0% description coverage, so the description must compensate for the sole entity_id parameter. The phrase 'entity's' implies that entity_id identifies the entity whose lockbox is being fetched, but no format, source, or additional parameter semantics are provided.

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 uses a specific verb ('Get') and a specific resource ('entity's lockbox mailing address'), and the parenthetical ('where payers send checks/EOBs') clarifies what a lockbox is. This clearly distinguishes it from siblings like lemma_get_entity and lemma_list_entity_mail.

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 intended use case is implied: call this when you need the address where payers send checks/EOBs for an entity. However, it does not explicitly state when not to use it or compare it with alternative sibling tools.

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