The Automators

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly explains the two-step interaction, the input requirement (answers array), and the output components (level, percent, breakdown, weakest dimensions, recommendations). It doesn't mention side effects, but an assessment is inherently read-only. It omits error handling and rate limits, but for this tool they are not critical.

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 two sentences with no fluff. The first sentence states the action, and the second gives a clear step-by-step usage pattern. All information is relevant and front-loaded, making it easy for an agent to parse and act on.

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 the tool's moderate complexity (two modes) and lack of an output schema, the description covers the essential workflow: how to get questions, how to submit answers, and what results to expect. It doesn't explain error cases, but for an assessment tool this is sufficient. Missing details like authentication are not relevant given the context.

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 already provides 100% coverage with a description of the answers array (integers 1-4, 10 items). The tool description adds meaning by explaining that the array represents scores per question and that omitting it returns the questions. This clarifies the parameter's role and the two-mode behavior beyond the schema's basic type/range.

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's function with a specific verb 'Runs' and resource 'AI Readiness Assessment'. It explains the two modes of invocation (no answers to get questions, with answers to get results), which distinguishes it from all sibling tools that serve different purposes like ROI estimation or content retrieval. No ambiguity remains.

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 provides explicit usage instructions: call with no answers first, then with answers after asking the user, and explains what to do with the results. While it doesn't name alternative tools, none of the siblings serve the same assessment function, so no exclusion is needed. The step-by-step flow gives clear context for when to use this tool.

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 provided, the description carries the full burden of behavioral disclosure. It explains the core behavior and additionally states what happens for out-of-scope inputs: 'Anything outside Canada and the US is served remotely and resolves to the locations index with a note.' This is meaningful behavioral context beyond the schema. It does not mention error handling or response format, but for a simple lookup tool this is adequate.

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 three sentences with no filler. It leads with the primary action, then adds the edge-case behavior, and ends with a clear usage directive. Every sentence earns its place.

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 is simple: one parameter, no output schema, no annotations. The description covers both in-region and out-of-region behavior and provides usage guidance. It does not describe the exact return value or structure, but given the simplicity and the absence of an output schema, the description is sufficiently complete for an agent to call it correctly.

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% because the query parameter already includes a description and examples ('A place, e.g. "Calgary", "Portsmouth, VA", "Ontario", "Berlin"'). The tool description reinforces the parameter's purpose by explaining how the place is resolved, but it does not add new semantic details beyond the schema. Thus the baseline of 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?

The description uses a specific verb and resource: 'Resolves a city, province, state or country to the matching local page' and explicitly states that it determines service status. It also distinguishes itself from siblings by clarifying its geographic scope (649 Canadian and US pages) and the special handling for outside regions. No other sibling tool appears to handle location-based service resolution.

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 an explicit trigger: 'Use it whenever a user mentions where they are.' This clearly tells an agent when to invoke the tool. It does not name alternatives or provide exclusions, but given the sibling list, this tool is unique in its purpose, so the guidance is sufficient.

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 clearly signals this is a computation/calculator tool and lists what it estimates, but it does not address side effects, data persistence, authentication, or what happens when no industry and no inputs are supplied.

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 sentences with no filler; the main action and outputs are front-loaded. The enumeration is long but each item contributes meaning, making it appropriately dense rather than vague.

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 no output schema and no annotations, the description covers the core inputs and outputs reasonably well. However, it leaves ambiguity about how the tool behaves when no industry and no parameters are provided, and it does not mention limits or fallback behavior beyond the preset.

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 the baseline is 3. The description names most parameters but adds little beyond what each property's description already states; it does mention the industry preset behavior, but the schema already documents that as well.

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 ('Runs the site's Customer Service Cost Calculator') and enumerates the key outputs. It is clearly distinct from abstract siblings like estimate_roi, though it never explicitly names a sibling for contrast.

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?

Provides a direct use case: 'Use it for support-desk cost questions.' This gives clear context for when the tool is appropriate, but it does not state conditions under which a sibling such as estimate_roi would be preferable instead.

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?

There are no annotations, so the description carries the transparency burden. It discloses the input-to-output calculation, the full set of returned values, the service recommendations, and the optional preset behavior. It doesn't explicitly state read-only semantics, but the calculator framing and 'the page shows' strongly imply a non-mutating operation.

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 sentences with clear front-loading: the operation, the outputs, and the use case. Every clause earns its place and there is no filler.

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, it's valuable that the description lists all returned values and the recommendations. Combined with the thorough input schema and explicit use case, an agent has enough context to invoke the tool correctly without further documentation.

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 the baseline is 3. The description paraphrases key inputs and notes the preset's effect, but it doesn't add meaningful semantic detail beyond what the input schema already provides.

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 ('Runs') with a concrete resource ('the site's ROI calculator') and enumerates the computed outputs, so an agent knows exactly what operation this is. The use-case sentence also helps disambiguate it from close siblings like estimate_customer_service_savings.

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 explicitly says when to use it: 'Use it when a user wants a number for the value of automating a process.' It provides clear context but does not list exclusions or name alternatives, so it stops short of a score 5.

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 well by specifying output format (markdown), the exact content structure, and the publishing source. It does not cover errors or auth, but for a simple public blog retrieval this is strong context.

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 with no filler, front-loading the return format and contents, then giving the necessary slug source and provenance. Every sentence earns its place.

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 single-parameter read-only retrieval with no output schema, the description sufficiently explains what will be returned and how to obtain the slug. Nothing critical is missing for an agent to invoke it correctly.

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%, and the schema already describes the slug as 'Post slug from search_content' with an example. The description repeats the search_content guidance but adds no new 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?

States a specific verb ('Returns') with a precise resource ('one blog post as markdown') and lists the included fields: title, author, date, full body, links, Sources list, and FAQs. This clearly distinguishes it from siblings like get_case_study or get_faq.

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?

Provides clear context by instructing the agent to use search_content first to find the slug before calling this tool. It does not explicitly mention exclusions or alternatives, but the prerequisite workflow is unambiguous.

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. It discloses the output format (markdown) and the content scope (facts, metrics, narrative). However, it doesn't mention potential rate limits, the need for authentication, or whether the content is static or dynamic, but for a simple read operation it's adequate.

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 one sentence, efficient, and front-loads the key fact (returns one case study in full) before adding specifics. The second sentence serves a practical purpose (where to get the slug). No fluff.

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 the tool is simple (one parameter, no output schema), the description is nearly complete. It defines what the tool returns and how to obtain the input. The only minor gap is not stating whether the output includes structured data beyond markdown, but that is not necessary for correct 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 single parameter 'slug' is fully described in the schema with an example. The description reinforces that the slug is an identifier required for retrieval, adding a practical hint (get from list_case_studies) that goes beyond the schema. Since schema coverage is 100%, a baseline of 3 would be standard, but the cross-reference to the list tool enhances usability.

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 returns one real case study in full, specifying content (facts, metrics, page narrative as markdown) and the resource (case study). It distinguishes from list_case_studies by indicating this is for a single detailed item, not a list.

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 instructs to get the slug from list_case_studies, which implies the correct prerequisite and alternative (list for discovery, this for detail). However, it doesn't explicitly state when not to use this tool (e.g., when you need a list) or mention other alternatives like search_content.

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. It clearly implies a read-only operation by listing the data returned and the purpose of checking facts, which suggests no side effects. It doesn't explicitly state 'read-only' or discuss response format, but for a zero-parameter getter this is adequately transparent.

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 front-loaded with the main action and content list, followed by concise usage guidance and exclusions. Every sentence earns its place with no filler, and the structure is logical: what → when → when not.

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, parameterless, read-only tool with no output schema, the description covers everything an agent needs: the exact content, usage intent, and sibling routing. There are no gaps that would hinder correct 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 tool has zero parameters and the schema is empty, so the baseline is 4 per the rubric. The description adds no parameter-specific information because none is needed; the lack of params 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?

The description states a specific verb ('Returns') and resource ('who The Automators are') and enumerates the exact data fields returned. It explicitly names the siblings it is not (get_pricing, get_contact_options), so an agent can distinguish it without opening other schemas.

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?

Provides explicit when-to-use ('to introduce the company or check a fact about it') and when-not-to-use with named alternatives ('not the place for pricing (get_pricing) or contact details (get_contact_options)'). This leaves no ambiguity about selection.

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 of behavioral disclosure. It clearly states that the server never sends messages and only returns options, which is a key behavioral trait for an agent deciding whether to invoke it. It does not discuss output format, but the listed contents partially compensate.

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 front-loaded with the core action ('Returns'), followed by a detailed but efficient list of contents, a clear usage directive, and a valuable side-effect clarification. Every sentence contributes meaningful information with no filler.

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, informational tool with no output schema, the description provides sufficient detail: what is returned, when to use it, and what side effects it avoids. Nothing essential is missing for an agent to select and invoke it correctly.

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 has zero parameters, so the schema fully covers the input side and no parameter documentation is needed. The description adds relevant context about what contact information is returned, which is appropriate for a parameterless tool.

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 that the tool returns contact options for reaching The Automators and enumerates the exact contents: phone, email, booking page, calendar link, hours, response-time promise, and inquiry guidance. This makes the tool's purpose unmistakable and distinct from the sibling info-retrieval 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?

The description explicitly says to use it whenever the user wants to talk to a human or book a consultation. It provides clear context for when to select this tool, though it does not name alternatives or explicitly say when not to use 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states what the tool returns and its content scope, including client-provided inputs, timeline, and the free consultation starting point. It does not list every possible output detail, but for a zero-parameter informational tool this is sufficient.

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 two sentences with no wasted words. The first sentence fully describes the returned content, and the second sentence gives the usage trigger. The most important detail 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?

For a no-parameter, no-output-schema informational tool, the description is complete. It tells an agent exactly what content to expect and when to invoke it. There is no missing information that would prevent correct selection or 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 tool has zero parameters and the schema is empty, so the baseline is 4. There is no parameter information needed; the description appropriately focuses on the fixed content of the response rather than parameter usage.

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 ('Returns') and names the exact resource: the four engagement steps, with concrete examples. It clearly distinguishes this tool from informational siblings like get_service or get_company_profile by focusing specifically on the engagement process.

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 explicitly identifies the intended use case: 'Use it for "how does working with you go" questions.' This gives clear contextual guidance, though it doesn't explicitly mention when not to use this tool or name alternative sibling 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add valuable nuance, such as the omission behavior ('Omit the topic for general plus pricing') and the slug-to-page mapping. However, it does not describe the return format, error behavior for invalid slugs, or any pagination/limits, leaving some ambiguity about what the agent will receive.

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 two sentences with no filler. The first sentence front-loads the core behavior and enumerates valid inputs, and the second states the use case. Every clause earns its place.

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 one-optional-parameter read-only tool, the description covers the essential facts: what it returns, which topic values work, the default when omitted, and when to use it. The lack of an output schema is partially mitigated by the intuitive nature of FAQs, but a bit more detail on the response shape would make it fully 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?

The schema already documents the topic values with examples, so the baseline is 3. The description adds the key semantic of omitting the parameter: it returns both general and pricing FAQs. This is not captured in the schema and meaningfully clarifies the optional parameter's behavior, elevating the score.

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 ('Returns') and resource ('the site FAQs'), and enumerates the exact valid topics. It clearly distinguishes itself from sibling content tools by scoping to FAQs for specific pages/slugs, and even states the intended use ('answer a common question in the site's own words').

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 provides a clear usage context: 'Use it to answer a common question in the site's own words.' It also implies when to prefer it over other content tools, though it does not explicitly name alternatives or state when not to use it. The context signals from siblings further clarify the decision, but explicit exclusions are absent.

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 behavioral disclosure burden. It makes clear this is a read-only retrieval operation and reveals an important boundary, 'illustrative example use cases (not client work),' that prevents confusion with case-study tools. It omits edge-case behavior such as handling of unknown slugs, but that is minor for a lookup tool.

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 the long enumerated list of content sections is informative rather than redundant. It is a single long sentence, but every listed element contributes to what the agent can expect from the tool, with no filler or restating of the 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?

For a one-parameter retrieval tool with no output schema, the description is largely complete: it states when to call it and what the return payload will contain. It does not explain how to discover valid slugs or how invalid slugs are handled, but the schema example and usage trigger cover most practical needs.

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 already provides 100% coverage for the single slug parameter, so the baseline is 3. The description adds the practical hint that the slug should be an industry name, but it does not add format, validation, or discovery guidance beyond the schema's 'healthcare' example.

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 starts with a specific verb ('Returns') and a specific resource ('the playbook for one industry'), then enumerates the exact content sections. It also distinguishes itself from siblings by clarifying that example use cases are illustrative, not client work, and by scoping the tool to a single industry rather than a list or general content type.

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 an explicit trigger condition: 'Use it when the user names an industry.' It does not name alternative sibling tools or list exclusions, but the single-industry scope and content list make the intended use clear enough for an agent to route correctly.

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 provided, the description carries the transparency burden. It discloses the content, the read-only nature implicitly, and adds an important behavioral note: figures come from the same module the site renders, so they should be quoted as given. This is useful beyond a simple one-line summary.

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?

Every sentence earns its place: the first defines the output, the second gives a direct usage instruction, and the third explains the data provenance and quoting behavior. It is compact despite covering many pricing facets.

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 description is complete for a zero-parameter informational tool. It covers what is returned, when to use it, and how to handle the returned figures. No output schema exists, but the description enumerates the return content clearly enough for an agent to know what to expect.

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 has zero parameters, and the schema coverage is 100%, so there is no parameter documentation burden. The baseline for a no-parameter tool is 4, and the description appropriately focuses on output content rather than 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?

The description opens with a clear verb and resource: 'Returns the pricing model' and then enumerates exactly what that includes. It also provides a usage trigger ('any cost, budget or "how much" question') that distinguishes it from related financial siblings like estimate_roi.

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 explicitly tells the agent when to use the tool: 'Use it for any cost, budget or "how much" question.' It does not explicitly name sibling alternatives or state when not to use this tool, but the context is clear enough for routing.

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 behavioral burden. It clearly discloses that this is a read operation returning a comprehensive bundle, including 'full page text as markdown,' which is a meaningful behavioral detail. It does not discuss potential errors, rate limits, or permissions, but for a simple getter these are less critical.

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, no filler. The first sentence front-loads the core behavior and return contents; the second provides usage context and the source for the slug. Every clause earns its place.

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 single-required-parameter read tool with no output schema, the description fully explains what the agent will receive: description, page markdown, FAQs, case studies, pricing, and timeline. It also gives the prerequisite step (list_services) and the usage trigger, making the tool complete from an agent's perspective.

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 a clear example in the schema. The description adds extra value by instructing the agent to obtain the slug from list_services, which clarifies where the parameter value comes from. This goes beyond the schema's static definition.

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 specific verb ('Returns') and resource ('everything the site says about one service'), then enumerates exact content types: description, markdown page text, FAQs, case studies, and pricing/timeline. This clearly distinguishes it from sibling tools like get_pricing, get_faq, or get_case_study by framing it as the composite service-detail endpoint.

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 explicitly says when to use it: 'when a user asks what a specific service involves or whether it fits their need.' It also tells the agent to get the slug from list_services. It does not explicitly name sibling tools that should be used instead for narrower questions, but the when-to-use guidance is clear.

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 provided, the description carries the full burden of behavioral disclosure. It does well by stating that the result set is fixed at four, that the case studies are 'real, published,' and that metrics are 'owner-confirmed,' which adds meaningful trust and caveat context. It stops short of explicitly stating that this is a read-only operation with no side effects, though 'Returns' strongly implies it.

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 carry a high density of useful information: return fields, fixed scope, authenticity, ownership of content, and a pointer to the sibling tool. The most important operational fact (what it returns) is front-loaded, and no words are 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?

For a simple, zero-parameter listing tool with no output schema, the description is complete: it tells the agent exactly what will come back, how many items, the nature of those items, and how to get more detail if needed. There is no ambiguity about invocation or interpretation.

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 has zero parameters and the schema is empty, so there are no parameter details to document. The description reinforces the fixed, non-filterable nature of the list by saying 'the four' case studies, which clarifies that no input is needed. This aligns with the baseline of 4 for zero-parameter tools.

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 ('Returns') with a clearly bounded resource: 'the four real, published case studies.' It enumerates the exact fields returned (client, industry, summary, owner-confirmed metrics, URL), making the tool's purpose unmistakable. It also distinguishes itself from the sibling get_case_study by explicitly noting that full stories belong to that 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?

The description provides explicit routing: 'These are the only pages that describe The Automators' own past work' sets the context for when this list is the right choice, and 'Use get_case_study for the full story' names the alternative and the condition for switching. This is clear, actionable guidance with no reliance on inference.

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 provided, the description carries the full burden of behavioral disclosure. It discloses the bounded result set (always 20 industries), the selection criterion ('dedicated playbook page'), and the exact returned shape. It does not describe potential errors or rate limits, but for a simple read-only list operation this is a minor omission.

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 concise sentences, no filler. The primary behavior and output fields are front-loaded, followed by a single clear usage directive. Every sentence earns its place.

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 list tool with no output schema, the description is complete: it says exactly what is returned, the fixed count, the included fields, and how the result should be used downstream. Nothing an agent needs to invoke it correctly 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 has zero parameters and the input schema is empty, so there is nothing to document. Per the baseline for 0-parameter tools, a score of 4 is appropriate because no parameter ambiguity exists and the description supplies the relevant contextual semantics about the output.

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 specific action ('Returns'), a precise resource ('the 20 industries with a dedicated playbook page'), and enumerates the output fields (slug, name, audience, one-line description, URL). It clearly differentiates this tool from siblings like list_services, list_case_studies, and get_industry_playbook.

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 explicitly names the intended use: 'Use it to find the slug for get_industry_playbook.' This directly tells an agent when and why to call this tool, and even identifies the dependent sibling that needs its output.

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 behavioral burden. The verb 'Returns' clearly signals a read-only list operation, and the description adds the exact contents and the boundary that pricing is excluded. It does not mention auth or rate limits, but for a zero-parameter read tool that is a minor omission.

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 with no filler: the first states the core output, the second gives the primary use case, and the third handles an exclusion. Every sentence earns its place and the most important information 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?

For a simple zero-parameter list tool, the description is complete: it specifies exactly what items are returned, what fields accompany each item, how to use the result, and which related tool to avoid. There is no output schema, but the described return shape is sufficient.

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 has zero parameters, so there is no parameter meaning for the description to add. Schema description coverage is 100% and the baseline for zero-parameter tools is 4. The description adds no parameter details, but none are needed.

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 the six service pillars and the eleven AI Agent Development capabilities, each with a one-line description and URL.' It clearly distinguishes itself from siblings by stating it is not for pricing and that get_service is the follow-up call.

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 explicitly says when to use it: 'Use it first to find the right service slug before calling get_service.' It also names the alternative for pricing: 'Not for pricing (get_pricing).' This leaves no ambiguity about which tool to choose.

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 clearly describes a read-only calculation/analysis behavior (runs the prioritizer and returns scores), and enumerates the output fields: score, priority, annual savings, reasoning, timeline, totals, and recommendations. It does not mention auth, rate limits, or side effects, but for a stateless computation tool this is sufficient.

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 followed by a usage sentence. It is efficient and covers the core action, inputs, and outputs. It lists many output details, which adds moderate density, but every sentence earns its place and the structure aids quick scanning.

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 no output schema and no annotations, the description does a strong job of covering what an agent needs to know: the input shape, the output contents, and the usage context. Minor gaps like validation limits or exact output formatting are already present in the input schema, so the description is nearly complete for correct 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?

Schema description coverage is 0%, but the description compensates by naming all input fields (name, hours per week, frequency, complexity, error-prone, people involved) and explaining how they map to the output. It adds meaning beyond the bare schema by clarifying that up to 10 processes are accepted and that results are ranked.

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 specific verb ('Runs'), the resource ('site's Process Prioritizer'), and the exact inputs and outputs. It distinguishes this tool from siblings like assess_ai_readiness or estimate_roi by focusing on prioritizing multiple manual processes with ranked scores and savings. It is not a tautology and gives a clear, unique purpose.

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 includes an explicit usage trigger: 'Use it when a user lists several things they might automate.' It does not name alternative tools to exclude, but the context is clear enough for an agent to know when to invoke this tool versus other assessment/estimation siblings.

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. It discloses that results are ranked and include specific fields, and notes TL;DR 'where available,' but does not state side effects (e.g., read-only) or any limits/auth requirements. For a search tool, the read-only nature is implied but not explicit, so 3 is appropriate.

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 sentences with no filler: front-loads the core search behavior, then the returned fields, then usage guidance. Every sentence adds 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 simple two-parameter search with no output schema, the description covers what it returns (type, title, URL, description, date, TL;DR) and when to use it. It doesn't specify whether the search is full-text or metadata-only, but this is a minor gap for a tool of this complexity.

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 query and limit are already documented in the schema. The description's mention of 'Keyword search' adds no parameter-level detail beyond the schema's own examples; 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?

Clearly states a specific verb ('Keyword search'), the resource ('content across blog posts, services, industries, tools and case studies'), and what it returns. The explicit mention of sibling tools get_blog_post, get_service, get_industry_playbook differentiates it from those readers.

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?

Provides explicit context: 'Use it to find the right page or post before reading it with' specific get_* tools. This names the alternative tools and the sequencing, though it doesn't state explicit when-not conditions or exclusions.

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