Professor Otter

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

Annotations already declare this as a safe, idempotent, non-destructive read, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the returned Markdown structure and the fact that puzzle PDFs include an answer key while game/drawing-practice PDFs do not.

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?

Three short sentences, front-loaded with the primary action and output shape, followed by the answer-key caveat and the parameter source. The answer-key sentence is slightly tangential but carries real decision value, so little is wasted.

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 an output schema present, the description need not document return values, yet it still orients the agent on output form and the answer-key distinction. Combined with the parameter-source hint, it is nearly complete for a simple two-parameter lookup, with only enum meaning left implicit.

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 50%: the slug parameter is documented in-schema with an example, while the activity enum has no per-value description. The description's contribution is telling the agent the values come from search_activities, which is helpful but does not explain what each activity type means.

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 one printable puzzle), names the return format (Markdown with description, level, word list or color key), and lists the accompanying play and PDF URLs. This is enough to distinguish it from sibling read tools like list_activities or show_word_search.

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?

Explicitly tells the agent where the required inputs come from: 'Use an activity and slug from search_activities.' That is a clear usage context, but it names no exclusions and does not contrast with alternatives such as show_word_search, so it stops short of full when/when-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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only the shape of the returned data (counts, levels, topics), which is largely redundant given an output schema exists.

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 core purpose is front-loaded and clear, but the 15-item parenthetical enumeration of activity types is bloated and largely recoverable from the tool's own output, adding length without decision value.

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 no-parameter list tool with full annotations and an output schema, the description covers purpose and entry-point usage adequately; only explicit sibling routing is 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly introduces no parameter concepts.

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 clear verb (List) and resource (printable activities) and enumerates what each entry carries: puzzle counts, levels, and topics. It does not explicitly contrast with siblings like search_activities or get_activity, though the exhaustive 'list everything' framing implicitly sets it apart from the search tool.

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?

'Start here to see what the site offers' gives an implied discovery/entry-point use case, which is useful routing guidance. However, it names no alternatives (search_activities, get_activity) and gives no when-not-to-use condition, so an agent must infer the boundaries itself.

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, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds value beyond them by disclosing the transaction boundary — purchasing happens out-of-band in a browser and payment details must never be collected — which is behavioral context the annotations cannot express.

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?

Three short sentences, front-loaded with what is listed, then the checkout constraint and the prohibition. Every sentence carries distinct information with no repetition of the title or annotations.

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?

An output schema exists, so return values need no explanation. For a parameterless catalog-listing tool whose annotations already carry the safety profile, the description adds the one thing structured fields cannot supply: the hand-off rule for payment.

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 the baseline applies; there is no parameter syntax for the description to clarify, and the empty schema is self-explanatory.

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 ('List the Professor Otter shop') and enumerates the catalog categories returned — printable PDF books, topic packs, the Everything Bundle — plus prices and availability. No sibling tool (all activity/word-search tools) overlaps this scope, so an agent can select it 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?

Gives explicit operational guidance: checkout is a browser page on the shop, send the person there, and never collect payment details or attempt the purchase. This clearly bounds the agent's role after listing, though it does not state when to prefer this tool over alternatives (a moot point given no overlapping sibling).

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 cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description nevertheless adds real behavior: grids grow to fit long words, errors enumerate the rule violations (too few words, >20 letters, word inside another), and a PDF with answer key is produced. It stops short of describing pagination/return shape, but the output schema exists.

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 tight sentences. The primary action and output are front-loaded, with input flexibility, edge behavior, and error semantics following in that order. Every sentence 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?

Given an output schema, the description needn't explain return values, and it covers input flexibility, grid-growth edge case, and error messaging. It leaves minor gaps on PDF link behavior and how the in-chat rendering works, but the picture is essentially 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 coverage is 100%, so the schema already documents seed, level, title, and words with enums and bounds. The description reinforces the array-vs-string flexibility and the grid-growth rule, but adds little the schema doesn't already state. Baseline 3 is appropriate.

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?

Specific verb (make/turn) + resource (word search) + input (spelling list), with concrete outputs named: a playable search in chat and a PDF link with answer key. Clearly distinct from siblings like show_word_search (view-only) and list_products.

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?

Establishes the trigger (a list of 4–20 words, like a spelling list) and covers accepting either a string or array. It does not, however, route the agent to alternatives such as show_word_search or clarify when to prefer one format over another.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral detail beyond them: the prefix-matching rule ('each query word must start a word in the puzzle'), the contents of each hit (PDF, play URL, slugs), and the answer-key caveat for puzzle vs game/drawing PDFs. It does not mention pagination or result limits.

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?

Five sentences, all substantive and front-loaded: matching semantics first, then filters, then return contents, then the answer-key caveat. The 'like the site's search box' analogy is compact and useful; the only minor cost is density, but nothing is wasted.

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?

Even though an output schema exists, the description explains what hits contain (PDF, play URL, slugs) and which sibling tools to chain into, plus the edge case that non-puzzle PDFs lack answer keys. Combined with full schema coverage and annotations, an agent has everything needed to call and use this 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 100% with enum values documented, so the baseline is 3. The description still adds meaning the schema lacks: how the query string is matched (word-prefix matching with the 'ant' vs 'Elephant' example) and that activity/level act as narrowing filters rather than required inputs.

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 (search) and resource (activities) with explicit scope: title, topic, or a word inside the puzzle. It even names the downstream siblings (get_activity, show_word_search) that consume the returned slugs, so an agent can tell what this tool is for versus browsing or fetching tools.

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?

Gives clear usage context: 'Narrow by activity or level if you like' explains the optional filters, and the mention of slugs for get_activity and show_word_search implies the chaining workflow. It stops short of naming alternatives such as list_activities or stating when browsing beats searching.

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 cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral value beyond them: the in-chat interactive play, words crossing off, the returned text grid and printable PDF link, and determinism across chat/site/PDF.

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?

Three tight sentences, front-loaded with the primary purpose and interactive behavior, then outputs, then the seed determinism note. No filler; each sentence 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?

An output schema exists, so return values need not be detailed, and the description still usefully previews them. For a read-only, closed-world tool with full param coverage, this is essentially 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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that seed yields a new grid and that slug+seed deterministically reproduce the same grid in all contexts, which the schema does not convey.

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 (show) and resource (word search) plus the interactive behavior ('a child can play in the chat: drag across the letters'). This implicitly contrasts with the sibling make_word_search, but the distinction is never made 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?

Offers partial guidance ('Pass a seed for a new grid'), clarifying when to supply a seed versus omit it, but gives no explicit when-to-use-this vs make_word_search or get_activity routing. Usage is 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.