company_supply

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

With no annotations, the description must carry the transparency burden, but it does not disclose side effects, permissions, or whether the tool is read-only. 'Apply it through the engine's guards' implies processing but leaves the outcome ambiguous.

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, demonstrating brevity. However, the cryptic wording sacrifices clarity, but conciseness is still satisfied in terms of length.

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 far from complete: it does not explain the tool's purpose, the meaning of any parameters, expected input/output, or any usage constraints. An agent would be unable to invoke this tool correctly based solely on the provided text.

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 lists six parameters with no descriptions, and the tool description does not explain any of them. Terms like 'bundle_json' and 'receipt_json' are not defined, and the description's mention of 'receipt' does not map explicitly to the 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 is vague: 'Hand one work item its receipt' does not clearly state the action, and terms like 'sealed observation, execution receipt, or proof' are undefined. The mention of 'engine's guards' hints at validation but not a specific operation.

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. The description lacks context, conditions, or examples that would help an agent decide to invoke it.

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