vendorping

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions the output format (CSV text) and fields, but does not disclose potential side effects, size limitations, or granularity of 'request history.' Basic behavior is clear but not deeply 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 a single, front-loaded sentence: 'Export the full vendor document report as CSV text (vendor, doc type, due date, status, request history).' It includes the action, format, and content in a compact structure with no wasted words.

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 parameterless export tool with no output schema, the description adequately explains what is returned (CSV with listed columns) and that it is the 'full' report. It does not mention any limitations or edge cases, but the scope is simple enough that this is reasonably 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 tool has zero parameters, so schema coverage is trivially 100%, triggering the baseline of 4. The description adds no parameter-specific semantics, but lists output fields, which is useful context though not parameter-related.

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 exports the full vendor document report as CSV text, with a specific verb (export), resource (vendor document report), and output format (CSV). It distinguishes from sibling tools like get_compliance_summary or list_missing_docs by emphasizing 'full' report.

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 for complete report export (via 'full') but does not explicitly contrast with sibling tools such as search_vendor_docs or get_expiring_docs. No when-not guidance or alternative recommendations are 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?

With no annotations, the description carries the burden of disclosing behavioral traits. It explains the content of the summary but does not explicitly state that the tool is read-only, safe to call, or any side effects. This is acceptable for a simple query tool but leaves some ambiguity.

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, well-structured sentence that front-loads the action and resource, then lists the included categories. No wasted words.

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 zero parameters and no output schema, the description fully explains the return values (totals for each category). It is complete for a straightforward summary tool.

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

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

There are zero parameters, so the baseline of 4 applies. The description appropriately focuses on what the summary contains rather than parameter details, since none exist.

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 it retrieves a compliance dashboard summary with specific categories (tracked, missing, expired/overdue, due this week, awaiting review). The verb 'get' and resource 'compliance dashboard summary' are specific and distinct from sibling tools that provide detailed lists or exports.

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 like list_missing_docs or get_expiring_docs. It only states the function, not the context or any 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?

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly notes that already-received documents are included, which is a non-obvious behavior. It also implies a read-only list operation. It does not detail response format or edge cases, but for a simple list tool this is reasonable.

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 sentence, approximately 25 words, with the action front-loaded and a purpose clause. No wasted words; it efficiently conveys scope, default, and expected use case.

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 (one optional parameter, no output schema, no annotations), the description covers the essential information: what it lists, the time window, the default, and the inclusion of received docs. It could mention result ordering or limit, but those are not critical for a straightforward listing tool.

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

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

Schema coverage is 100% for the single 'days' parameter, and the description echoes the default of 30 without adding new semantic meaning. The description does not explain the parameter beyond what the schema already states, 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 lists vendor documents expiring within a configurable time window, with the added nuance of including already-received documents. This distinguishes it from sibling tools like list_missing_docs (which focuses on missing docs) and search_vendor_docs (which is a general search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: it is for proactive renewal management ('so renewals can be requested before they lapse'). It does not explicitly name alternatives or exclusion criteria, but the purpose is sufficiently implied given the sibling tools. A higher score would require explicit 'use instead of X' guidance.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add meaningful behavior beyond the name: the exclusion of received documents and the priority ordering (expired/overdue first, then by days remaining). However, it does not mention return format, pagination, or any potential error cases, so it is not fully 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 a single, well-structured sentence that front-loads the primary verb and resource, then adds a concise ordering rule. Every word contributes to understanding, with no fluff or repetition.

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 low complexity (zero params, no output schema, no annotations), the description covers the core behavior and ordering. It does not specify the exact output shape, but the tool name and verb make the list semantics obvious. The missing details are not critical for a simple list operation.

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 nothing to explain. Per the rubric, zero params earns a baseline of 4. The description does not need to add parameter semantics because none exist.

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: 'List every vendor document that is still missing (not yet received)' with a specific ordering rule ('most critical first — expired/overdue at the top, then by days remaining'). This distinguishes it from sibling tools like search_vendor_docs and get_expiring_docs.

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 clear context for when to use the tool: whenever the user needs to see all missing vendor documents. It does not explicitly mention alternatives, but the purpose and ordering make the use case evident. No exclusions are stated, but the specificity of 'every vendor document ... still missing' implies it is the go-to for listing missing items.

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 the output shape (status, expiry dates) but does not explicitly mention that the operation is read-only, that the query is optional, or any case-insensitivity/shorthand behavior (though the latter is in the param schema). This is adequate but has clear gaps.

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 short sentences that get straight to the point. It states what the tool does and what it returns without any fluff or 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 simple one-parameter search tool with a well-described schema, the description provides sufficient context. It covers the core action and return values. The optional query behavior is documented in the schema, so the absence from the description is not a major gap. The lack of an output schema is compensated by listing return fields directly.

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 description provides 100% coverage for the single parameter, explaining case-insensitivity, shorthand support, and the 'omit to list everything' behavior. The tool description only adds 'vendor name or document type', which is redundant with the schema. Baseline 3 is appropriate.

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

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

The description uses a specific verb ('Search') and resource ('tracked vendor documents'), and clearly specifies search by vendor name or document type. It also mentions the return payload (status and expiry dates), which distinguishes it from sibling tools like list_missing_docs or get_expiring_docs.

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 this tool (when searching for vendor documents by name or type). The input schema adds a key usage hint ('Omit to list everything'), but the description itself does not explicitly state when not to use it or mention alternatives such as get_expiring_docs.

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