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

Annotations already declare the read-only, idempotent, non-destructive profile, so the safety bar is met. The description adds genuinely useful context beyond the annotations: the SuperAdmin authorization requirement and the fact that payoutDetails.details is masked in the response.

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 terse sentences with no filler; the lookup keys come first, followed by the auth constraint and the masking note. Every sentence carries distinct information.

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 single-entity read tool with no output schema and full annotation coverage, the description covers the essentials: what it retrieves, the auth requirement, and a notable response-masking behavior. It could be marginally stronger by noting the list alternative or partial-result behavior.

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 description coverage is 100%, so the baseline is 3. The description restates 'by farmId or slug' but the schema documents three parameters including vendorFarmId, and the text does not clarify the relationship between farmId, slug, and vendorFarmId, so it adds little over the schema.

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?

Specific verb+resource ('Get one Rent-a-Hatch vendor') with the lookup keys named ('by farmId or slug'). The singular 'one' implicitly distinguishes it from the sibling list_rentahatch_vendors, though it never names that sibling explicitly.

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?

Provides the 'SuperAdmin only' access prerequisite but gives no explicit when-to-use guidance or exclusion criteria, and never names list_rentahatch_vendors as the bulk alternative. Usage must be inferred from the singular/plural distinction.

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