Find or create animal by EID

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write surface is known. The description adds meaningful context beyond that: it creates on no-match, requires Editor access, and warns of explicit-intent gating. It does not state what is returned (found vs newly created) or idempotency behavior, keeping it short of a 5.

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 sentences, front-loaded with the operation and its side effect, followed by prerequisites and the alternative. No filler.

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 no-output-schema, two-param tool with annotations covering safety, the description covers purpose, side effect, prerequisite, and sibling disambiguation. Only the return semantics (whether the existing animal or the new one is returned) are absent, a minor 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 both parameters (eid, farm_id) are already documented in the schema. The description only reinforces the EID lookup concept and adds no syntax, format, or default-farm nuance beyond the schema baseline.

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+resource (find or create an animal by EID) and immediately clarifies the dual nature of the operation. Names the sibling read tool it must not be confused with, so an agent can differentiate without opening schemas.

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?

Explicitly states when-to-use (when intent to create inventory exists), the prerequisite (Editor access), and the alternative ('Use lookup_animal_by_eid for reads'). Clear routing with no inference required.

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