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

Beyond the readOnlyHint/destructiveHint=false annotations, the description adds genuinely useful behavior an agent cannot get from structured fields: the report lags 24-48 hours behind check-ins or deletions, fees are not charged automatically, and a Cotlet API key with app access is required. This is the kind of context that prevents misinterpreting stale or fee-free results.

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?

Four sentences, all load-bearing and front-loaded: purpose, definition of terms, freshness caveat, billing note, auth prerequisite. Slightly dense but no filler or restatement of the tool name.

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 carries the return-value burden and does so (member rows from the report), and it adds freshness, billing, and auth context. Nothing essential for calling this read-only reporting tool correctly appears to be missing.

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%, with from/to and the type enum (including its default of all) already documented in the schema. The description only gestures at the date range and does not add syntax or format detail beyond the schema, so the baseline 3 applies.

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 a specific resource (the No Show / Late Cancel report) and scope (a date range), then defines both sub-types: members who missed a class or cancelled inside the late cancel window. An agent can distinguish this reporting tool from siblings like pushpress_get_class_roster or pushpress_list_classes without opening a schema.

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?

Usage is implied by the date-range framing and the freshness caveat, which tells the agent results for recent classes may be incomplete. However there is no explicit when-to-use versus when-not guidance, and no sibling (e.g. get_class_roster for live attendance) is named as an alternative.

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