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

With no annotations, the description carries the full behavioral burden, and it does disclose one real trait — the bearer-key auth requirement, which the schema does not encode. However it never confirms read-only/non-mutating behavior, idempotency, pagination, or how large 'every issue found' can get, leaving meaningful gaps for an unannotated 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 short sentences, front-loaded with the returned content before the auth caveat. Nothing is padded, though the terse phrasing borders on under-specification rather than tightness.

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, the description usefully enumerates what comes back and notes the auth requirement, which is enough to attempt a call. It still omits when the tool is appropriate and any detail on the undocumented record_id, so completeness is only minimum-viable.

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 0% for the single parameter, so the description must compensate. 'For one record' only loosely signals that record_id identifies a single record; it adds no format, source, or expected-value guidance (e.g. ID shape, where to obtain it).

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 names the concrete payload of the tool — totals, a per-category breakdown, and every issue — scoped to 'one record.' That is far more specific than a restated name, though it never states the verb and never differentiates itself from siblings like get_rules or check_hours.

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 when-to-use guidance at all: no statement of which situations call for a record summary versus add_entries, check_hours, or get_rules. 'Requires a bearer key' is a prerequisite, not usage routing, so an agent gets no help choosing between this and its siblings.

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