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

With no annotations, the description carries the full burden, and it does add one real behavioral fact: a bearer key is required for auth. However, it says nothing about read-only semantics, error behavior, or response shape, leaving significant gaps for a no-annotation tool.

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?

Two compact sentences with the returned-content list front-loaded and no filler. Slightly terse to the point of omitting parameter context, but structurally efficient.

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?

With no output schema, listing the returned fields is valuable and partially compensates, and the auth note is useful. But the undocumented required parameter and absent usage guidance leave the definition only minimally complete for a data-fetch tool.

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 0% for the single site_id parameter, and the description never mentions site_id or what it identifies. 'For one record' hints at a single-target lookup but does not connect the required parameter to the record, so the schema gap is not compensated.

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 enumerates the returned content (events, flagged issues, last inspection and pump-out, next dates) for a single record, making the resource concrete. The verb is only implied by the name rather than stated, and no sibling (e.g., check_service_record) is named for contrast, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus siblings like check_service_record or get_rules. Usage is only inferable from the content list; no exclusions or prerequisites beyond the bearer key are given.

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