FulfillmentInbound_listPlacementOptions

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

No annotations are provided, so the description carries the behavioral burden. It does indicate that this is a list-style read operation and that it runs in a different deployment ('not here'), which is useful context. However, it does not mention prerequisites, authentication needs, required inbound-plan identification, or what the list response contains.

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 short and mostly scannable, but the first sentence 'Catalog entry' is vague and does not earn its place. The core purpose is stated only in the final sentence, so the structure is not ideally front-loaded.

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 zero-parameter, no-annotation, no-output-schema tool, the description is too thin. It never explains how the agent identifies the inbound plan, whether placement options must first be generated, or what kind of data will be returned. The deployment caveat is useful but does not make the tool fully actionable.

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 zero parameters and 'additionalProperties: true', so there are no defined parameters for the description to clarify. The phrase 'for an inbound plan' adds a small amount of conceptual context, and with 0 params the baseline is 4.

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 names a specific verb and resource: it 'Provides a list of all placement options for an inbound plan.' This is clearly a list operation and distinguishable from generate/confirm placement options, though it does not explicitly call out those siblings. The opening 'Catalog entry' and 'Runs in your Kuudo deployment, not here' adds some ambiguity about whether the tool is actually callable.

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?

There is no guidance on when to use this tool versus FulfillmentInbound_generatePlacementOptions, confirmPlacementOption, or listInboundPlans. The only context is that it runs in the Kuudo deployment rather than here, which is an execution-location note, not a when-to-use explanation.

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