invoicevista

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds valuable context beyond annotations: it specifies the returned data is 'safe metadata' and enumerates omitted fields (contact, legal-entity, address, banking, integration), and constrains results to the authenticated organization's business. This informs the agent about content filtering without contradicting annotations.

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

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

One sentence, front-loaded with the action and resource, with zero wasted words. The key scoping constraint and field omissions are stated immediately, making it easy for an agent to parse quickly.

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

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

For a simple read-only get operation with one parameter and an existing output schema, the description is complete. It states what the tool does, what fields are omitted, and the ownership constraint. No critical information needed for correct invocation 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 single parameter businessId is fully documented in the schema with a clear description (24-character lowercase hexadecimal id) and a pattern. Since schema coverage is 100%, the description adds no additional parameter-specific meaning, meeting the baseline of 3.

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

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

The description states a specific verb ('Get'), a resource ('business'), and a clear scope ('one business owned by the authenticated InvoiceVista organization'). It also lists omitted field categories, distinguishing it from other get/list tools and clarifying what the operation 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 clearly implies this tool is for retrieving a single business's safe metadata, excluding sensitive fields. However, it does not explicitly name alternatives or state when not to use it (e.g., when sensitive fields are needed or when listing all businesses). The context is clear but lacks explicit exclusions.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context by explicitly stating that it returns only aggregates and never exposes identifiers, contacts, tax ids, addresses, notes, or free text. This goes beyond the annotations and is critical for privacy-aware use.

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 primary action and scope are front-loaded, and the data exclusion clause follows naturally. It is concise, structured, and fully digestible at a glance.

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 a read-only aggregation with an output schema provided. The description covers the purpose, data scope, time constraints, and privacy exclusions. Given the annotations and schema, 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?

Schema coverage is 100%, and each parameter (businessId, startDate, endDate) has a clear description in the schema. The tool description adds the 'at most 366 UTC days' constraint, which is not in the schema, but this is a minor addition. Overall, the description does not significantly enhance parameter understanding beyond the schema.

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

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

The description states a specific verb (summarize), a clear resource (quote pipeline), and defines the scope (non-draft, counts, values, status mix, one tenant-owned business, at most 366 UTC days). It clearly distinguishes itself from siblings like get_receivables_summary or get_revenue_summary, which target different data domains.

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 when to use the tool by specifying the exact subject matter (quote pipeline for a single business) but does not explicitly name alternatives or state when not to use it. Usage is inferred from the resource type, but no direct comparison to sibling tools is provided.

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?

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), it discloses that partially paid invoices are excluded from money totals and explains why, and lists a broad set of never-returned data categories. This gives an agent strong expectations and prevents attempts to retrieve detail.

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: purpose, key aggregation caveat, and explicit output exclusions. The necessary caveats are front-loaded and 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?

Given a single parameter and an output schema, the description provides enough context: scope, aggregate-only behavior, and explicit non-inclusion list. No critical usage gap remains.

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 businessId with 100% coverage; the description only restates the 'one tenant-owned business' scope, adding no extra format or semantic detail. Baseline 3 is appropriate given high schema 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 states a specific verb ('Summarize') on a specific resource ('receivables') with defined scope (open, overdue, age-bucketed, one tenant-owned business). The title and description align, and the tool is clearly distinct from sibling summary tools like get_revenue_summary or get_quote_pipeline_summary.

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 use when an aggregate receivables view for a business is needed, but offers no explicit comparison to siblings or conditions for choosing get_revenue_summary or get_quote_pipeline_summary. It provides context on output limits but no 'when not to use' 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 establish readOnly/idempotent/non-destructive behavior, so the bar is lower. The description adds valuable boundaries beyond those annotations: it explicitly excludes invoice, payment, customer, and identifier data, and states that it cannot execute or advise on a financial transaction.

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 tightly written sentences with no filler. The main function is front-loaded, followed by data-boundary and safety clarifications, each earning 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 read-only summary tool with a rich output schema and full parameter descriptions, the definition covers scope, date-window limits, aggregate-only behavior, and the non-transaction boundary. There is no missing operational detail that would prevent 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 coverage is 100%, so the schema already documents businessId, startDate, and endDate. The description adds operational semantics by constraining the range to at most 366 UTC days and clarifying that businessId is a tenant-owned business, improving selection and invocation without repeating parameter definitions.

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/resource pair, 'Summarize invoice production and recorded payments,' and narrows scope to one tenant-owned business over a bounded UTC date range. It further distinguishes itself from sibling detail tools by stating it returns aggregate counts and amounts only, never item-level or identifier data.

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 conveys a clear context: use it for aggregate revenue summaries over a date window, not for itemized data or executing financial transactions. It does not name sibling tools like get_receivables_summary or get_quote_pipeline_summary explicitly, so the alternatives are implied rather than spelled out.

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, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: it explains the fallback to Free tier when no active or past-due subscription exists, and reassures that payment-processor credentials are never returned. This goes beyond the annotations and gives the agent confidence about edge-case 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 three short sentences, each conveying a distinct piece of information: the main action, the fallback behavior, and the security guarantee. It is front-loaded with the core purpose and has zero filler, making it effective and easy to parse.

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, return values are already specified, and annotations cover the operational profile. The description completes the picture by explaining the fallback logic and the non-return of sensitive data. For a single-parameter, read-only tool, nothing needed for correct invocation 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 input schema has 100% coverage for the single parameter businessId, including a pattern and descriptive text. The description adds no extra parameter-specific meaning, but the schema already fully documents it, so 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 clearly states the tool retrieves the current billing plan and quota limits for a specific tenant-owned business, using a specific verb ('Get') and a concrete resource. It distinguishes itself from sibling tools by focusing on subscription data, and the fallback note adds specificity about the returned state.

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 this tool is for retrieving subscription information for a single business, but it does not explicitly compare to alternatives like get_business or list_businesses, nor does it state when to prefer this over other tools. The purpose makes the use case clear, but explicit routing or exclusion guidance is 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?

Adds context beyond annotations by clarifying that the returned data is limited to safe metadata and explicitly enumerates sensitive fields that are excluded. This goes beyond the readOnlyHint, idempotentHint, and destructiveHint annotations, which already convey safety. The description does not mention pagination mechanics or authentication, but the core behavioral trait (what is and isn't returned) is well disclosed.

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, zero fluff. The primary purpose and scope are front-loaded in the first sentence, and the important exclusion list is in the second. Every word earns its place, and it is appropriately concise for the tool's simplicity.

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 quite complete for a simple list tool: it states the operation, scope, and exclusions. With an output schema present, return details are covered there. The main gap is the lack of explicit pagination guidance (how to use cursor, when to fetch more pages), though 'bounded page' implies it. Given the tool's low complexity and the presence of an output schema, this is only slightly under-specified.

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 input schema has 50% description coverage: cursor has a description, but limit does not. The tool description adds no meaning for either parameter—'bounded page' hints at pagination but doesn't explain limit semantics or the relationship between cursor and limit. Since coverage is moderate and the description fails to compensate for the undocumented limit, this is a clear gap.

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 ('List'), a resource ('businesses'), and the scope ('bounded page of safe business metadata' for the InvoiceVista organization). It also explicitly lists what is omitted (addresses, contact details, payment settings, secrets), making it easy to distinguish from sibling tools like get_business or list_products. The purpose is unambiguous and differentiating.

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 usage when a page of non-sensitive business metadata is needed, but it does not explicitly state when to use this tool versus alternatives like get_business or show_business_overview. No exclusions or alternate routing are provided. The guidance is implicit rather than explicit, so it only meets the 'implied usage' level.

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, and destructiveHint, so the description does not need to restate safety. It adds meaningful behavioral context by indicating pagination ('bounded page') and an authentication requirement ('authenticated organization'), which are not in the annotations.

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

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

A single sentence that is front-loaded and contains no filler. Every phrase contributes meaning: 'bounded page' signals pagination, 'safe' aligns with read-only behavior, 'product catalog metadata' identifies the resource, and 'authenticated organization' scopes the 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?

For a simple paginated read-only listing tool, the description plus the rich annotations, input schema, and output schema provide everything an agent needs. Return values are covered by the output schema, and safe behavior is covered by annotations, 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 schema covers businessId and cursor with descriptions, leaving limit only structurally defined. The description adds some meaning by hinting at pagination ('bounded page') and organization scoping, but it does not explicitly explain how limit and cursor relate to the listing behavior, so it only partially compensates for the schema's 67% 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 uses a specific verb ('List') and resource ('product catalog metadata'), and adds scope ('for the authenticated organization'). It clearly distinguishes this from sibling tools like list_businesses and get_subscription by naming the exact resource being listed.

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 useful context ('bounded page', 'safe product catalog metadata', 'authenticated organization') but does not explicitly state when to use this tool versus alternatives such as list_businesses or get_receivables_summary. Usage is implied rather than made explicit.

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, and non-destructive behavior. The description adds meaningful behavioral context beyond that by disclosing the data boundary: it will never return identifiers, exact amounts, contacts, PCI/bank data, credentials, or payment actions. No contradiction with annotations.

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. The first sentence states the main deliverable, and the second selectively enumerates exclusions. Information is front-loaded and 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 one-parameter, read-only tool with a full input schema and an output schema, the description covers the aggregate nature and the privacy/data boundary well. The only slight gap is that it leaves the distinction from sibling summary tools somewhat implicit, but the negative clause plus annotations make the call safe and effective.

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 only parameter, businessId, is fully documented in the input schema with type, pattern, and tenant-owned semantics. The description weakly echoes 'tenant-owned' but adds no new parameter-level meaning, so the baseline of 3 is appropriate given 100% schema 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 opens with a specific verb ('Render') and a clear resource: a bounded tenant-owned business snapshot with aggregate counts and a product-catalog preview. The explicit 'Never returns individual...' clause distinguishes it from detail-oriented siblings like get_business 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?

The description implies usage through 'bounded tenant-owned business snapshot' and the negative scope ('Never returns individual...'), so an agent can infer it is for high-level aggregates rather than detail lookups. However, it names no alternatives and gives no explicit when/when-not conditions relative to sibling summary tools.

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