NOGA Movement

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful content scope by naming the topics returned: offerings, pricing basics, and key links.

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 a single front-loaded sentence with no wasted wording. It immediately communicates the tool's content scope.

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 zero-parameter informational tool with annotations covering safety and no output schema, the description gives enough about what topics the response covers. It could be slightly more complete by clarifying that it does not provide live schedules or perform bookings.

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?

There are zero parameters, so parameter semantics are not a meaningful differentiator. The baseline score of 4 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 clearly identifies this as an informational overview of NOGA Movement covering offerings, pricing basics, and links. It is easy to distinguish from siblings like book_class or get_class_schedule, though it uses a noun phrase rather than an explicit verb.

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: this is the general-information tool rather than a booking, schedule, or instructor-search tool. However, it does not explicitly state when to use it instead of checking services, schedules, or teacher trainings.

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

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

Annotations already declare the write, non-idempotent, open-world, destructive profile, so the description's real contribution is the two-step flow: this call only holds a spot and hands back a checkout link where payment or a pack/membership is applied. That is valuable context an agent would otherwise assume away, but it omits hold expiry, whether repeat calls create duplicate holds, and what happens if the link isn't used.

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 tight sentences with the core action and return value front-loaded, followed by the prerequisites. Nothing is repeated and no filler appears.

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 correctly explains the return value (a checkout link) and the downstream confirmation step, which is the key thing an agent needs to relay. Remaining gaps — hold duration, failure modes, and sibling selection versus book_session — are minor but real for a booking mutation.

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%, so every parameter is already documented, and the description mostly restates that service_id/event_id come from get_class_schedule and that first name and email are required. It adds no format, validation, or optional-field guidance (phone, last_name) beyond the schema, so 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?

"Holds a spot in a live NOGA class for a person and returns a nogamovement.com checkout link" states a specific verb and resource, and the "live class" framing implicitly separates it from the 1:1 book_session sibling. It never names book_session or explains which to pick, so an agent must infer the distinction.

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?

The description gives a concrete prerequisite chain: the service_id and event_id must come from get_class_schedule, plus the person's first name and email. It provides clear context for when the call is valid but offers no exclusions (e.g., when to use book_session instead) and no note on retry/repeat behavior.

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

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

Annotations already flag destructiveHint=true, openWorldHint=true and non-idempotence; the description adds genuine value by explaining the two-step hold-then-pay flow through nogamovement.com and that payment happens off-tool. It stops short of saying how long the hold lasts or what happens if the slot is taken or the person never pays.

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 dense sentences with zero filler, and the most important fact — that this only holds a time and returns a checkout link — is front-loaded.

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 correctly explains what is returned (a checkout link) and why. The remaining gap is hold expiry and failure behavior for a destructive, open-world mutation, which the agent would benefit from knowing.

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%, so all seven parameters are already documented. The description only restates which fields are required and their provenance from get_session_times, adding no new meaning; 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?

Names a specific verb and resource ('Holds a private session time') and, crucially, discloses that it does not finalize the booking but returns a checkout link. 'Private session' implicitly separates it from the sibling book_class, 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?

States a clear prerequisite: service_id, start and end must come from get_session_times, which tells the agent the correct call ordering. It gives no explicit exclusion or alternative for group classes, so the agent must infer that book_class handles those.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that results come from an "official directory," a useful source-authority note, but it discloses nothing about result cardinality, ordering, or what an unfiltered call returns, which matters since no parameters are required.

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?

One sentence, front-loaded with the verb and resource, then the filter scope. Every clause carries information and nothing is padded or repeated.

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 two-parameter, read-only, non-destructive lookup with full schema coverage, this is close to sufficient. The main residual gap is that there is no output schema and the description does not sketch what a result contains or how many come back, plus the unspecified behavior when called with no arguments.

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 both parameters are already documented including example location formats like 'Denver' and 'Weston, Florida'. The description merely restates the same two filters and adds no new semantics, such as whether location matches city, state, or both, or how the filters combine.

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 pairs a specific verb ("Searches") with a specific resource ("the official directory of Pilates+ certified instructors") and states the two available scopes: city/state or online. That is enough to separate it from verify_pilates_plus_instructor semantically, but it never names the sibling or explicitly contrasts lookup vs verification.

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 only implied: the agent can infer it should call this when it needs to locate instructors, and the two filter modes suggest when each param applies. There is no explicit statement of when to prefer this over verify_pilates_plus_instructor, no mention of what happens if both filters are omitted, and no exclusions.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered and the description is free to add value beyond it. It does: it discloses the returned fields, the Eastern timezone convention (a real gotcha for scheduling), and that booking ids are included, which tells the agent this is a safe, non-mutating pre-booking read. It omits anything about result volume or ordering beyond 'upcoming'.

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?

A single front-loaded sentence that packs the resource, the scope, the field list, the timezone, and the downstream purpose with zero filler. Nothing could be removed without losing 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?

There is no output schema, so the description must carry the return shape, and it does by naming times/timezone, availability, price, and ids. With three optional, fully schema-documented parameters and clear safety annotations, only the lack of explicit routing against get_session_times keeps this from being complete.

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 all three parameters (days, from_date, class_name) are already documented with defaults and an example in the schema. The description adds nothing parameter-specific, which is acceptable at full coverage but earns only the baseline.

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 uses a specific verb and resource ('Returns upcoming live NOGA classes') and enumerates the payload (times in Eastern, spots left, price, booking ids). It is clear about what it does, but it never names or distinguishes itself from the sibling get_session_times, leaving the class-vs-session boundary for the agent to infer.

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 only implied: 'the ids needed to book' hints that this precedes book_class, but there is no explicit when-to-use statement or exclusion relative to get_session_times, get_teacher_trainings, or list_services. The agent can guess the discovery-then-book flow but must infer it.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful scope context (availability is limited to Laurie's private session offerings), but says nothing about timezone handling, whether slots are cached or live, or how results are bounded by the days/from_date window.

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?

A single front-loaded sentence that states the resource and scope with no filler. The service enumeration is somewhat long but it conveys real domain vocabulary an agent may need to match caller phrasing.

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 simple read-only lookup with full schema coverage, the definition is adequate but thin. With no output schema, the description could have said what an 'open time' looks like (date, time, slot length, timezone) and whether an empty result is possible; instead the agent must discover the return shape empirically.

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 all three parameters (days, service, from_date) are already documented in the schema with defaults and formats. The description adds no constraint or format detail beyond listing example service names, so the baseline of 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 gives a specific verb+resource ('Returns open times for a private session with Laurie') and enumerates the service types, which implicitly distinguishes it from the class-oriented siblings like get_class_schedule. It stops short of explicitly naming book_session or list_services as the companion tools, so the differentiation is inferred rather than stated.

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 only implied: an agent can infer this is the availability check that precedes book_session, but the description never says when to use it versus get_class_schedule or how it relates to list_services. No prerequisites, exclusions, or alternative routing are stated.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the content returned (price, inclusions, enroll link) and that the result set is a fixed, small catalog, which tells the agent this is a cheap static lookup.

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?

A single sentence with zero filler, front-loaded with the verb and the primary program, and the parenthetical field list is compact rather than redundant.

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 parameters and no output schema, the description carries the burden of describing returns, and it does so for the main certification (price, inclusions, enroll link) though less explicitly for the NOGA Foundation and Define Barre entries. For a simple static catalog lookup this is close to sufficient, with only the exact per-training fields for the latter two left unspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for parameterless tools applies. The description correctly implies no filtering is needed because the catalog is enumerated in full.

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?

States a specific verb ('Returns details of') and a specific resource (teacher certification trainings), then enumerates the three programs covered and the key fields (price, what's included, enroll link). None of the siblings (class schedule, session times, services, instructors) overlap, so an agent can route unambiguously.

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 domain: this is the tool for certification/training questions rather than class booking, which the sibling names make easy to infer. However, it never states when to prefer it over list_services, which could plausibly also surface trainings, nor any exclusions.

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

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context beyond that by stating the result payload (price, length, description) and asserting completeness ('every bookable'), which matters since there is no output schema; minor gaps remain on pagination/ordering.

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?

One compact front-loaded sentence with no filler; the parenthetical examples earn their place by disambiguating what a 'session' is.

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 one-optional-param list tool with no output schema, disclosing the returned fields and the catalog scope is close to sufficient. The missing piece is any acknowledgment that results can be narrowed via the `kind` filter.

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% and the single `kind` parameter has an enum with its own description, so the schema does the work. The description adds no meaning beyond it — it never mentions the class/session/all filter, so 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?

Names a specific verb and resource ('Lists every bookable NOGA live class and private session') and clarifies scope with examples (readings, mentorship). It implicitly separates itself from schedule-oriented siblings like get_class_schedule and get_session_times, but never names them, so differentiation is inferential rather than explicit.

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 only implied: 'bookable' suggests this is the catalog-discovery step before book_class or book_session, but the description never states when to use this instead of get_class_schedule/get_session_times. No exclusions or prerequisites are given.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context by naming the authoritative source ('official directory') and the 'active listing' condition, but it does not say what a result looks like (boolean vs. detail record) or how name matching behaves.

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?

One front-loaded sentence with no filler and nothing redundant. It is efficient, though the brevity leaves gaps that a second short sentence could have closed.

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?

This is a low-complexity, single-parameter, read-only tool with full schema coverage and no output schema, so the burden is light. Still, the description never indicates the shape of a verification outcome or the failure mode for unlisted/uncertified names, which is the main thing an agent needs before calling it.

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?

With one parameter at 100% schema coverage, the schema already defines 'name' as the instructor's full name. The description adds nothing about matching strictness, formatting, or handling of duplicates and partial names, so it stays at the baseline.

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?

States a specific verb (checks/verifies) and a specific resource (Pilates+ certified instructor status in the official directory), including the 'active listing' criterion. It implicitly contrasts with find_pilates_plus_instructor (verify a known person vs. discover instructors) but never names that sibling, so differentiation is inferable rather than explicit.

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 only implied: you supply a person's name to confirm certification. There is no statement of when to prefer this over find_pilates_plus_instructor, no note on prerequisites, and no guidance for the ambiguous case of a name that returns no match.

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