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 implies a read-only operation via 'List' but does not explicitly state that no data is modified, nor does it disclose rate limits or any other behavioral constraints. It does explain pagination parameters, which helps, but for a tool with zero annotations, a bit more explicit disclosure (e.g., 'This is a read-only operation') would be ideal.

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 efficient: one sentence for purpose, followed by a clean, tabulated Args block. There is no redundant phrasing, and the key information is front-loaded. Every line 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?

Given that an output schema exists, return values are covered. The description covers the operation and parameters sufficiently. It does not mention any edge cases (e.g., empty results, error handling) but for a simple list tool this is acceptable. The sibling context and lack of nested objects keep the complexity low, so the description is complete enough.

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 description provides detailed explanations for all four parameters that go well beyond the schema. It clarifies that 'page' is zero-based, 'size' is the number of results, 'sort' follows a specific format ('name,asc'), and 'name' is a partial match filter. With 0% schema coverage, this is a strong compensation—an agent can correctly construct calls without needing additional context.

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 verb 'List' and the resource 'companies in the Pax8 partner account'. This unambiguously distinguishes it from sibling tools like pax8_list_company_contacts (contacts) and pax8_list_invoices (invoices), leaving no doubt about what this tool returns.

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 makes it obvious when to use this tool—whenever a list of companies is needed. It does not explicitly name alternatives or conditions for not using it, but because all siblings are for different entities, the context alone provides sufficient guidance. A small mention of 'use this for companies, not contacts' would make it a 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?

No annotations are provided, so the description must disclose behavioral traits. The description states 'List contacts', which implies a read-only operation, but it does not explicitly confirm that it is non-destructive, nor does it mention any permissions, rate limits, or output format details. The description adds minimal behavioral context beyond the verb itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the main purpose, and structured as a docstring with clear parameter explanations. Every sentence adds value; there is no redundancy or unnecessary detail. It is appropriately sized for a simple list operation.

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 simplicity, an output schema exists (though not shown), so the description need not explain return values. The description covers the purpose and all parameters. It could add details about error handling or required permissions, but for a straightforward read-only list operation with well-documented parameters, it is sufficiently 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 has 0% description coverage, but the description thoroughly explains each parameter: company_id as the unique identifier, page as zero-based with a default, and size as results per page with a default. This adds significant meaning beyond the schema's types and defaults, fully compensating for the lack of schema-level descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists contacts for a specific company, using a specific verb and resource. It differentiates from sibling tools like pax8_list_companies by specifying the resource is contacts and that it is scoped to a company. The purpose 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?

The description implies the tool is for retrieving contacts for a company, which is distinct from listing companies, invoices, or other resources. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The usage context is clear from the name and description but lacks explicit 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 of behavioral disclosure. It only states the operation and parameters, without mentioning error conditions, auth requirements, rate limits, or side effects. It does not contradict any annotations, but adds minimal behavioral context beyond the obvious list action.

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 extremely concise, with the purpose front-loaded and each sentence earning its place. It avoids unnecessary verbosity and clearly lists parameters in a structured format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values are covered there. The description explains pagination semantics and the required invoice_id. For a simple list tool, it provides all essential information an agent needs to call it correctly. Minor gaps like error handling are not critical for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does: each parameter gets a brief explanation, including that page is zero-based and size is per-page count. This adds meaning beyond the bare schema fields, though not deeply.

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 action (list), resource (line items), and scope (specific invoice). This distinguishes it from sibling tools like pax8_list_invoices or pax8_list_subscriptions, which target different resources.

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 usage context is implied: use this tool when you need line items for a specific invoice. However, there is no explicit guidance on when not to use it or how it compares to alternatives such as pax8_list_invoices or pax8_list_usage_summary_lines.

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. It accurately describes a read-only listing operation but does not explicitly mention side effects, error behavior, or pagination limits beyond the parameter defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, with a short opening line followed by bullet-like parameter explanations. No unnecessary information is included.

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 provides enough contextual detail for an agent to invoke the tool correctly, including parameter semantics and defaults. Since an output schema is available, not describing the return structure is acceptable, though a brief note on expected errors or authorization could make it slightly more 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?

All five parameters are described clearly, including defaults, the zero-based page index, and examples for sort and status filters. This fully compensates for the 0% schema description coverage.

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 purpose: listing invoices in the Pax8 partner account. It provides a specific verb and resource, distinguishing it from related tools like invoice items.

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 explains the parameters and gives examples, but it does not explicitly state when to use this tool versus sibling tools such as pax8_list_invoice_items. The intended usage is implied by the name and parameters, but not explicitly contrasted with alternatives.

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 present, and the description does not disclose any behavioral details such as read-only nature, side effects, rate limits, authentication requirements, or error behavior. The description adds no transparency beyond the raw operation name.

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 extremely concise, containing only the essential purpose statement and parameter explanations. No redundant or irrelevant content is present.

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 lacks information about return format, pagination behavior beyond the parameter defaults, filtering semantics, ordering rules, or error conditions. Given that the schema covers only parameter shapes and no output schema is shown, the description leaves major functional gaps for an agent.

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 provides only parameter names and types with zero description coverage. The description adds some semantic context by providing examples (e.g., sort 'orderDate,desc', status values) and explaining defaults, but it does not fully specify valid values, formats, or relationships between parameters.

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 action ('List') and the resource ('orders') within the Pax8 partner account. It does not explicitly differentiate from sibling list tools, but the resource 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?

No guidance is provided on when to use this tool versus alternatives like pax8_list_subscriptions or pax8_list_invoices. The description only lists parameters without explaining context or conditions for use.

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?

The description uses 'List', which implies a read-only operation, and provides parameter descriptions that clarify behavior. With no annotations provided, the description alone conveys the non-destructive nature, though it does not explicitly state side-effect-free or idempotent behavior.

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 brief and to the point, containing only the action, resource, and a compact parameter list. There is no redundant or filler 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?

The description provides enough context for a straightforward list operation, including parameter semantics and an example for sort. It does not describe the return format, but for a simple listing tool the output is likely self-explanatory, and the presence of an output schema mitigates this gap.

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?

Each of the five parameters is described in the Args section with clear semantics: page (zero-based), size (results per page), sort (field and direction with example), vendor_name (partial match filter), and product_name (partial match filter). This fully covers the schema parameters and adds meaning beyond their titles and defaults.

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 action ('List products') and the target resource ('Pax8 marketplace'), distinguishing it from sibling tools that list other entities like companies, invoices, or subscriptions.

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 indicates it is a listing operation with optional filters and pagination parameters. It does not explicitly contrast with alternative tools, but the resource name 'products' is sufficiently specific to avoid ambiguity with 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 of explaining behavior. It lists the basic function and parameters, but does not disclose pagination behavior, sort format details (beyond an example), or potential errors, leaving some behavioral aspects unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, with a single introductory sentence followed by a clear parameter list. No unnecessary information is included.

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 simplicity and the presence of an output schema, the description is nearly complete. It could add a note about default pagination or listing behavior, but the core use case is fully covered.

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 description text provides a clear explanation for every parameter (page, size, sort, company_id, status, product_id), including valid status values and an example for sort. This adds significant meaning beyond the schema titles and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists subscriptions within the Pax8 partner account, using a specific verb and resource. It is easily distinguishable from sibling tools that list companies, invoices, products, etc.

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 no explicit usage guidance, but the resource type (subscriptions) and available filters make it obvious when to use this tool versus siblings. It could improve by mentioning that it is the appropriate choice for subscription-related queries.

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 only states the action and lists parameters, with no disclosure of behavior beyond pagination defaults. It does not mention whether the operation is read-only, potential error conditions, rate limits, or any side effects. For a list operation this is minimal; the description is not misleading but leaves much to inference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with a single introductory sentence followed by a structured Args block. It is efficient and avoids redundancy. The Args section is front-loaded with parameter semantics, and there is no filler. It could be more concise by removing the docstring format, but it is appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema (not shown), so return format does not need to be explained. However, the description lacks any mention of pagination behavior beyond defaults, error handling, or any special cases like empty results. For a simple list tool with one required parameter, this is adequate but not thorough. The presence of sibling tools for related operations is not addressed, leaving the agent to guess when to use this specific one.

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 description adds meaning beyond the schema: it explains 'page' as 'Zero-based page number for pagination' with a default, and 'size' as 'Number of results per page' with a default. 'subscription_id' is described as 'The unique identifier of the subscription,' which clarifies its role. Since the schema itself has no parameter descriptions (coverage 0%), this description compensates by defining each parameter's purpose and default behavior.

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 the action ('List usage summaries') and the scope ('for a specific subscription'), which is clear. It does not explicitly differentiate from the sibling tool pax8_list_usage_summary_lines, but the phrase 'for a specific subscription' implies a per-subscription focus, distinguishing it from a broader usage-summary-lines tool. This is slightly more specific than a generic 'list' but lacks explicit sibling 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?

The description provides no guidance on when to use this tool versus alternatives such as pax8_list_usage_summary_lines or pax8_list_subscriptions. There is no mention of prerequisites, typical use cases, or conditions that would favor this tool. The agent must infer usage from the name alone.

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?

The operation is described as 'List', which implies a read-only, non-destructive action. However, with no annotations provided, the description does not explicitly disclose any side effects, pagination behavior, or rate limits beyond the parameter documentation.

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 brief, containing a one-line summary followed by a clean parameter list. No redundant information or 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 that the tool is a list operation and the context indicates an output schema exists (though not shown), the description is sufficient. It does not specify the return format, but this is standard for list endpoints and not critical for invoking the tool 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 description explains all three parameters (usage_summary_id, page, size) with clear, concise semantics, covering exactly what each controls. This fully compensates for the schema's lack of per-property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a specific verb ('List') and resource ('usage summary lines') for a given usage summary, distinguishing it from sibling tools that list companies, invoices, or other resources.

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 purpose is obvious from the resource name, but the description does not explicitly state when to prefer this tool over alternatives (e.g., when you have a usage_summary_id and need line items). It is implicit rather than explicit.

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