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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safe, read-only nature is known. The description adds the bulk support behavior but doesn't disclose potential edge cases like pagination defaults, date format requirements, or response size. Given the annotations, a score of 3 is appropriate—it adds some value but not full transparency.

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?

The description is concise (three lines plus a bulk support note) and front-loaded with the primary purpose. Every sentence adds value: the first defines the tool, the second covers filtering, and the third mentions bulk. No fluff or redundancy.

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?

The tool has 7 parameters, no output schema, and annotations only cover safety (read-only, idempotent). The description is short and doesn't cover critical usage details like pagination semantics (skip/take), date format expectations, or the distinction between member_id and member_ids. For a list tool with multiple parameters, this is insufficient for an agent to use it effectively without guessing.

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%, so the description must compensate for parameter meanings. However, the description only mentions member_id(s), start_date, end_date as filters, but doesn't explain skip, take, or account, which are likely pagination and tenant scoping. It also doesn't mention that exactly one of member_id/member_ids is needed or the semantics of date ranges. The description adds minimal parameter semantics, so a score of 2 is warranted.

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 clearly states the tool lists gym entries (check-ins / turnstile access) and mentions optional filtering by member and date range. It distinguishes itself from siblings like evo_member_list and evo_activity_list by specifying the domain (gym entries), but it doesn't explicitly contrast with a similar list tool, so it doesn't fully earn 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?

It mentions 'optionally by member and date range' and 'Bulk support', indicating when to use it (listing entries) and hinting at batched usage, but it doesn't explicitly state when not to use it or provide alternatives (e.g., for member details use evo_member_get). The guidance is implied rather than explicit.

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