AI Inventory Network

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds context about generating a checklist but does not disclose additional behavioral traits such as how the 'request' input is used or what the output contains. This is acceptable but not extensive.

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. It is concise and contains 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 simple tool with only two parameters and an output schema, the description provides enough context for the tool's purpose and usage. However, the complete lack of parameter explanation leaves a gap. The annotations and output schema help, but the description could have clarified the expected input content.

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 not explicitly explain the meaning of 'request' or 'supplier'. While the overall purpose hints that 'request' is the user's context for the checklist, it does not clarify the role of the parameters, leaving the agent to infer.

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: generating a checklist of information required before listing inventory. It uses a specific context ('Use this when a user wants...'), which conveys the action and resource. It does not explicitly compare to siblings, but the described purpose is distinct from the sibling 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 states when to use the tool: 'when a user wants a checklist of information required before listing inventory.' This gives clear contextual guidance. It does not mention when not to use it or list alternatives, but for a tool with clear scope, this 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about the scope (assessing margin) but does not describe the output format or any internal behavior, so it adds some but not rich value.

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 is front-loaded with the usage condition and contains no filler. It is 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?

Although an output schema exists (so return values need not be explained), the description fails to explain the meaning or usage of the two parameters. With zero parameter documentation, an agent cannot reliably construct a valid request, making the tool 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 no descriptions, and schema description coverage is 0%. The description does not mention the 'request' or 'supplier' parameters at all, leaving the agent without any guidance on what values to provide. This is a major 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 says 'Use this when a user wants the inputs required to assess potential listing margin,' which indicates the tool provides required inputs but does not clearly state the action (e.g., 'returns', 'generates'). It is more specific than a tautology and distinguishes from siblings by mentioning margin assessment, but the exact behavior remains vague.

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 'Use this when...' statement, making the intended use case clear. However, it does not mention alternatives or when not to use the tool, so it lacks the exclusions that would earn 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?

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds a use case but no additional behavioral context (e.g., how the checklist is generated, any constraints). It does not contradict the annotations, so a mid-range score 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?

The description is a single, concise sentence with no wasted words. It clearly front-loads the purpose and provides an immediate trigger condition.

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 (2 params, output schema exists), the description is adequate but minimal. It covers the primary use case but does not clarify what 'request' should contain or any edge cases. The lack of parameter guidance leaves some ambiguity 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?

Schema description coverage is 0%, and the description does not explain any parameters. The required 'request' and optional 'supplier' are left entirely unspecified, so the agent must rely on names alone. The description fails to compensate for the lack of schema 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?

Description clearly states the tool generates a 'supplier intake checklist' for 'inventory or travel/resort offers', which is a specific action and resource. It distinguishes from siblings like 'create_listing_requirements' by focusing on intake checklists rather than listing requirements or margin fields.

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 a clear usage context ('Use this when a user wants a supplier intake checklist...'), which implies when to use it. It does not explicitly mention alternatives or exclusions, but the purpose is distinct enough from siblings to avoid confusion.

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, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds minimal behavioral context beyond the outcome; it doesn't describe what exactly happens during normalization or whether any external data is accessed. This is acceptable given strong annotations but adds little extra value.

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 is front-loaded with the usage trigger. It contains no unnecessary words and 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?

While the output schema exists and annotations cover safety, the description fails to explain how to construct the request or what the optional supplier parameter does. Given the zero schema coverage, the description should compensate but does not, leaving the tool functionally under-specified for an AI 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?

Schema description coverage is 0%, and the description provides no guidance on the meaning of 'request' or 'supplier'. The description only mentions 'inventory fields' but does not map them to the request parameter, leaving the required parameter entirely unspecified. The agent cannot determine what to put in 'request' from the description.

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: normalizing inventory fields into a consistent listing structure. The verb 'normalize' and resource 'inventory fields' are specific, and the outcome is defined. It distinguishes from sibling tools like create_listing_requirements or generate_supplier_intake by focusing on normalization rather than creation or intake.

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 starts with 'Use this when...' which provides explicit usage context for user intent. However, it does not mention any exclusions or alternatives, so it doesn't fully guide against using siblings. Still, the condition is clear and practical.

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