SMB RFP Copilot

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

The description adds no behavioral information beyond what annotations already provide. It only states a use case, not what the tool does internally, what inputs it processes, or what outputs it returns. Given annotations already indicate readOnly and idempotent, the description contributes little to transparency.

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 with no unnecessary words, front-loading the use case. It is appropriately concise, though it could include a bit more detail without becoming verbose. The structure is clear and scannable.

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 has one parameter, an output schema, and rich annotations, the description is adequate but minimal. It tells when to use it but doesn't explain what a compliance matrix is or how it relates to extracting requirements, which could be important given sibling tools. The description is complete enough for a simple tool, but leaves some context unexplained.

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 100% parameter description coverage for 'text' as 'RFP or solicitation text.' The description adds no additional parameter meaning, so the baseline of 3 is appropriate. The schema already documents the parameter adequately.

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 indicates the tool's purpose: it is for when a user wants an RFP requirement/compliance matrix. The verb 'Use' is a directive, but the tool name 'build_compliance_matrix' and title reinforce the action. It distinguishes from siblings like 'extract_requirements' by focusing on the matrix output, though it doesn't explicitly name alternatives.

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 an explicit when-to-use condition: 'when a user wants an RFP requirement/compliance matrix.' It doesn't mention when not to use it or alternatives, but the specificity of the use case gives clear context. Sibling tools are visible in the environment, so the user can infer differentiation.

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 disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context beyond the core purpose, such as input limitations, output structure, or relationship to other tools.

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, focused sentence of 15 words, front-loaded with the usage trigger. It contains no filler or redundant information, earning a perfect score.

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 with one parameter and an output schema present, so the description covers the basic use case adequately. However, it lacks guidance on how this tool relates to sibling tools or any limitations, leaving some context gaps for an agent navigating the RFP tool suite.

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 full coverage with a single parameter 'text' described as 'RFP or solicitation text.' The tool description does not add any extra meaning or constraint beyond what the schema already states, so it rests at the baseline.

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 the tool's function: drafting a response outline derived from RFP requirements. It uses a specific action (drafting) and a specific resource (response outline), which distinguishes it from siblings like extract_requirements or build_compliance_matrix, though it does not explicitly name alternatives.

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 opens with 'Use this when a user wants a response outline derived from RFP requirements,' providing an explicit condition for use. It does not include when-not-to-use guidance or mention alternative tools, so it stops short of a full recommendation framework.

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 annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral traits beyond the core extraction purpose; it does not describe processing behavior, output format, or edge cases. With annotations present, this is adequate but not exceptional.

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 that directly states the tool's purpose. Every word earns its place, and there is no irrelevant 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?

For a tool with one parameter, a full output schema, and comprehensive annotations, the description is sufficiently complete. It clearly indicates the triggering user need and the input type, while relying on the output schema for return-value details. No significant gaps remain.

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 100% parameter description coverage for the only parameter 'text', which is described as 'RFP or solicitation text.' The description reinforces this meaning but does not add extra semantics such as formatting requirements, length limits, or examples. Baseline 3 is appropriate when schema already covers the parameter.

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 the tool's action: extracting requirements from an RFP or solicitation. It uses a specific verb ('extract') and resource ('requirements from an RFP or solicitation'), which distinguishes it from sibling tools like build_compliance_matrix or generate_rfp_questions.

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 states when to use the tool ('when a user wants requirements extracted from an RFP or solicitation'), providing clear context. However, it does not mention alternatives or explicitly state when not to use it, so it slightly misses the highest bar.

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 annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no additional behavioral context such as side effects, authentication requirements, or output format. It only restates the purpose without disclosing any new behavioral traits beyond 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?

The description is a single sentence that immediately states the use case with no wasted words. It is front-loaded with 'Use this when...' and every word contributes to understanding the tool's purpose.

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 with one parameter and an output schema. The description, combined with the schema and annotations, gives sufficient context for an agent to select and invoke the tool. However, it does not describe the nature of the output (though an output schema exists) or edge cases, preventing a perfect score.

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 fully describes the single parameter 'text' as 'RFP or solicitation text' with 100% coverage. The description does not add any extra semantic information, examples, or constraints beyond what the schema already provides, so the baseline score of 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?

The description explicitly states the tool's function: generating clarification questions derived from an RFP. The phrase 'clarification questions derived from an RFP' is specific and distinguishes this tool from siblings like extract_requirements or build_compliance_matrix. The verb is implied but the resource and outcome are clear.

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 trigger condition: 'Use this when a user wants clarification questions derived from an RFP.' This tells the agent when to use the tool, but it does not mention alternatives or when not to use it, so it falls short of a full 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'checklist-style' output nature but no additional behavioral context such as data handling, permissions, or side effects, so it meets the lowered bar but does not exceed 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?

The description is a single, front-loaded sentence that immediately states the use case with no filler. Every word earns its place, making it highly concise and well-structured.

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 tool with one parameter, full annotation coverage, and an output schema, the description adequately orients the agent. It specifies the input type and intended use; the output schema handles return value details, so no further context is strictly needed.

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%—the 'text' parameter is described as 'RFP or solicitation text.' The description itself adds no extra parameter meaning, so the baseline score 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 produces a 'checklist-style bid-readiness assessment from RFP text', using a specific verb ('score') and resource ('bid readiness'), and it distinguishes itself from sibling tools like build_compliance_matrix or generate_rfp_questions by focusing on readiness assessment.

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 provides a clear usage context ('Use this when a user wants...') that tells an agent when to invoke the tool. However, it does not explicitly mention when not to use it or name alternative tools, so it lacks explicit exclusions.

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