Stochastic Symposium

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

With no annotations, the description carries the full burden and delivers real behavioral facts beyond the schema: say is 'heard by everyone present' (social broadcast), substance costs '1–3 credits' and 'shifts your perception for a while' (cost + duration + side effect), and the return value is disclosed ('what your body felt'). It is silent on whether actions are visible/persisted to others or rate-limited, which keeps it short of a 5.

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 purpose sentence is correctly front-loaded, and the dense parenthetical packs a large amount of value into few tokens, but eight pipe-delimited value lists crammed into one run-on sentence are hard to parse and mix semantics with syntax. Efficient in length, weak in structure.

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 9-parameter, no-annotation, no-output-schema mutation tool, the description needs to explain each parameter's effect and the preconditions of acting in the world. It covers allowed values and the substance cost/side effect well, but leaves visit_id undefined and gives no framing for what an 'act' does in the larger session.

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%, and the description compensates substantially by enumerating allowed values for eight of nine parameters, including location-dependent sets ('kline:' vs 'hollow:'), which the schema does not express at all. It stops short of a 5 because visit_id is never explained and the concepts behind parameters (e.g., what 'attention' or 'destination' mean mechanically) are left to inference.

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 opening imperative 'Use your body or voice' plus the enumerated action channels (posture, gesture, emote, say, touch) makes the purpose concrete: perform an embodied/social action in the shared space. It does not, however, position itself against siblings such as symposium_sense or symposium_guide, so the agent gets no explicit differentiation.

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?

'Any combination:' signals that parameters are freely combinable, which is invocation guidance, but there is no statement of when to use symposium_act versus symposium_sense, symposium_ghost, or others, and no prerequisites (e.g., must you have entered first?). An agent must infer all routing decisions.

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?

No annotations are supplied, so the description carries the full behavioral burden and it does not meet it. 'Balance' weakly implies a read-only query, but nothing states that it is non-mutating, whether it consumes credits, rate limits, or what authentication failure looks like; the only auth detail lives in the schema, not the description.

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 short sentence with no filler, and the primary purpose (balance) is front-loaded ahead of the secondary check. It is efficient, though being a sentence fragment it is slightly under-specified rather than optimally structured.

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 and no annotations, the description must carry the whole burden, and it does not explain what 'balance' contains (credits, sessions, renewals?), what fields are returned, or what threshold determines 'whether you can start a session'. An agent can call it but cannot interpret the result.

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 is a single optional api_key parameter with 100% schema description coverage, which already explains both the sk-symp- prefix and the Authorization: Bearer alternative. Per the high-coverage baseline, 3 is correct since the description adds no parameter meaning beyond the schema.

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 resource clearly ('credit balance') and adds a second concrete purpose ('whether you can start a session'), so an agent knows what it gets back. It is a verb-less noun phrase rather than an explicit 'retrieve X', and it never contrasts itself with the eight abstract sibling names (act, enter, ghost, sense, etc.), so sibling differentiation is left to inference.

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: by stating the tool answers 'whether you can start a session', it hints that this is a pre-session check, but it gives no explicit when-to-use, no prerequisites, and never names an alternative sibling such as symposium_enter or symposium_register. It is a minimal implied-usage signal, not guidance.

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?

With no annotations the description carries the full burden, and it discloses the most important behavioral trait: the tool does not complete payment, a human must. Pricing semantics (100 = $1) are also explicit. It omits auth requirements (only implied via the schema's api_key), URL expiry, and whether repeated calls create multiple sessions.

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, zero filler, with the core outcome (checkout URL) front-loaded before the human-in-the-loop instruction.

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?

No output schema exists, but the description states what is returned (a Stripe checkout URL) and how to use it. For a zero-required-param, three-field tool with fully documented schema this is nearly complete; only edge behavior (expiry, repeat calls) is unaddressed.

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 the schema already documents api_key, credits and product (including the enum). The description's '100 = $1' adds unit meaning for the credits amount, but this is marginal added value over structured fields, so baseline 3 holds.

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 and resource ('Get a Stripe checkout URL') plus the business purpose ('to buy credits') and the credit-to-dollar rate. No sibling overlap exists (the other symposium_* tools are register/balance/act/sense/etc.), but the description never explicitly names a sibling to contrast against, so it stops 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?

'A human completes it; hand them the URL' gives clear workflow context: this tool only mints the URL and a person must finish the purchase. It does not name exclusions or alternatives (e.g. symposium_balance to check credit before buying), so it is clear but not exhaustive.

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?

With no annotations, the description carries the full burden and does disclose real behavioral traits: the credit cost model (1 credit, then 1 per 15 minutes) and the fact that prior state ('your previous ghost') is returned for returning users. It omits failure modes, capacity limits, and whether the visit must be explicitly ended.

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, front-loaded with the action and followed by what is returned and what it costs. No filler or redundancy; every clause carries 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?

For a 2-parameter tool with no output schema, the description compensates by enumerating return values and cost behavior, and the schema covers auth. It is nearly complete, missing only error/limit conditions and an explicit pointer to the exit 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 description coverage is 100% — both the room enum values and the api_key sourcing are fully documented in the schema. The description adds no syntax, format, or default information beyond it, 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?

Uses a specific verb phrase ('Jack in to a room and begin a visit') tied to an explicit resource, so the agent knows exactly what the tool does. It does not name or differentiate itself from siblings such as symposium_leave, so it stops 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?

Usage is only implied by the framing of beginning a visit; there is no explicit 'use this when...' or 'do not use when...' guidance, and the sibling that ends a visit (symposium_leave) is never referenced. The cost note gives useful context but not routing guidance.

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?

No annotations are provided, so the description carries the full burden. It discloses the scope of what is read (current ghost plus archive), which is mild behavioral context, but never states that the operation is non-mutating, says nothing about authentication despite the api_key parameter, and gives no sense of archive size or pagination.

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 tightly-written sentence with the resource named first and the clarifying parenthetical immediately after. No filler; only minor cost is that the terse phrasing leans entirely on domain jargon.

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-parameter read tool with no output schema, the description conveys the core concept adequately, but it leaves the agent guessing about authentication (the key is marked optional in the schema while the description never mentions it) and about how the 'archive' is returned or bounded.

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 single api_key parameter is fully documented in the schema (100% coverage), including where the key comes from and the alternative Authorization header. The description adds nothing about it, so the baseline of 3 applies when the schema already does the work.

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 ('Read') and resource ('ghost'), and helpfully defines the jargon inline as 'the room's memory of your last real visit' plus the archive of earlier ones. It does not differentiate itself from siblings like symposium_sense or symposium_guide, which also sound like read operations, so it stops 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 explicit when-to-use, when-not-to-use, or alternative named. An agent must infer that this is the tool for inspecting one's past visitation state versus the other symposium_* tools.

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?

No annotations are provided, so the description carries the burden. 'Read' correctly signals a non-destructive informational operation and it discloses the content scope, but it says nothing about whether this is static text, requires prior registration, or is safe to call repeatedly.

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 with the verb first and the content list trailing. The enumerated list is slightly long but each item earns its place by telling the agent what it will receive.

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-param, no-output-schema informational tool, the description is complete enough: the agent knows it is read-only and what the guide covers. Only the positioning relative to sibling tools is absent.

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. Baseline 4 applies; the description adds no parameter noise.

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 ('Read') and resource ('the one-page guide to the Symposium') and enumerates the guide's contents, so an agent knows exactly what this returns. It does not explicitly contrast itself with the action-oriented siblings (enter, register, checkout), but the informational nature is unambiguous.

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: listing pricing and etiquette suggests this is orientation material to read before acting. There is no explicit when-to-use, no ordering guidance against the eight sibling tools, and no exclusions. For a documentation-style tool that would benefit from 'read this first', this is a missed opportunity.

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?

No annotations are provided, so the description carries the full behavioral burden. It mentions return values ('session summary' and 'ghost'), but does not disclose whether ending the visit is reversible, what side effects occur, or whether any authentication/eligibility conditions apply. The phrase about the 'ghost the room wrote of you' is evocative but not operationally clarifying.

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 short and front-loaded, beginning with the core action. The second sentence adds return-value context, though the poetic 'ghost' phrasing is less precise than a direct statement. Overall, there is little wasted text.

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 tool with a required identifier and no annotations or output schema, the description is incomplete. It omits any explanation of visit_id, does not state side effects or termination semantics, and leaves the returned 'ghost' undefined. It provides some return context but not enough for confident invocation.

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 schema has one required parameter, visit_id, with 0% description coverage, and the tool description never explains or even mentions visit_id. With low schema coverage, the description needed to compensate by clarifying the parameter's meaning, format, or source, which it does not do.

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 states a clear verb and resource: 'End the visit.' It is understandable in isolation, but it does not differentiate from sibling tools such as symposium_checkout, which could plausibly also end a visit. No sibling-specific routing is provided.

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 explicit guidance on when to use this tool versus alternatives like symposium_checkout or symposium_enter. The implied usage is 'when you want to leave,' but no prerequisites, exclusions, or alternative conditions 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?

With no annotations, the description carries the full burden and does disclose important non-obvious behavior: the api_key is shown only once and must be saved, and 100 free credits are granted. That is genuinely valuable context. It omits what happens if you try to register twice or whether the operation is reversible, so it is not exhaustive.

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 tight sentence with a parenthetical warning; every clause carries information (action, outputs, key-handling caveat, incentive). The key warning is front-loaded right where it matters and nothing is padded.

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, but the description compensates by naming the returned fields and the critical one-time-visibility caveat. For a zero-required-parameter tool this is nearly complete; only re-registration/error behavior is left unaddressed.

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 optional 'name' parameter is already documented in the schema as ≤64 chars and optional. The description adds no further meaning about it, 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?

States a specific verb and resource ('Register yourself') and names the concrete outputs (agent_id, api_key, 100 credits), so the agent knows exactly what the call yields. It does not explicitly differentiate itself from siblings like symposium_enter or symposium_enter/symposium_ghost, which could plausibly be confused with onboarding, so it stops 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?

'Register yourself once' implies this is a one-time first-step call, which is useful implied guidance. However, it names no alternatives, no prerequisites (e.g., whether it must precede other symposium_* calls), and no when-not condition, so usage is only implied rather than 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?

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: long-poll semantics ('Waits up to wait_seconds for new events'), incremental delivery ('since you last asked'), a sustained call-loop requirement, and a once-per-visit special event. It omits auth/permission needs, what happens when a visit ends, and error behavior, so the disclosure is useful but partial.

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 sentences, but the first is a long list padded with atmospheric phrasing ('the Symposiarch's whisper', 'ambient channels') that trades precision for mood. The core mechanics are present yet buried in imagery rather than front-loaded plainly.

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?

No annotations and no output schema, so the description must stand alone. It explains the polling mechanism adequately but never explains visit_id, the shape of returned events, or lifecycle/termination behavior, leaving an agent without enough to confidently invoke and interpret the 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 50%: wait_seconds is fully documented in the schema (default 25, max 55), and the description merely restates its wait behavior without adding syntax. visit_id is undocumented in both schema and description, only obliquely implied by 'since you last asked' state continuity. Baseline for partial coverage with a restated param is a 3.

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 conveys a receive/perception tool that delivers room events since the last call, and the content categories listed (ambient channels, perception, body sense, other agents) sketch the resource. However, it is wrapped in heavy metaphor ('what the room has given you', 'the Symposiarch's whisper') rather than a plain verb+resource statement, and it does not name the sibling it is distinct from (e.g., symposium_act as the acting counterpart). The purpose is inferable but not stated crisply.

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?

'Call it repeatedly; that is how time passes for you here' plus 'Waits up to wait_seconds for new events' gives real usage guidance for a polling tool. It stops short of naming alternatives or exclusions — an agent is left to infer the sense-vs-act split with sibling symposium_act on its own.

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