company_marketplace_supply

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

The description hints at side effects ('supplied proofs are verified and provider effects remain external') but does not explain whether the tool reads, writes, advances state, or has destructive behavior. The safety profile is unclear, especially given the 'advance' wording.

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 and not overly verbose. However, it uses dense jargon and lacks concrete detail, so the conciseness does not translate into clarity.

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 complex parameter surface and lack of schema descriptions, this description is far from complete. It does not explain parameters, return behavior, or the operational lifecycle it references, leaving an agent without enough context to use the tool correctly.

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?

None of the seven parameters are described in the schema or the description. Critical parameters like 'operation', 'entity_ref', 'bundle_json', and 'payload_json' have no explained meaning, making correct invocation impossible.

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 gives a broad high-level purpose ('inspect or advance marketplace supply') but does not specify a concrete verb or resource. Phrases like 'scoped lifecycle' and 'supplied proofs are verified' are ambiguous and do not clearly differentiate this tool from many similar company_* and marketplace actions.

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. There is no mention of prerequisites, conditions, or context that would help an agent decide between this and the many sibling marketplace/company tools.

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