FbaInventory_getInventorySummaries

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

Without annotations, the description must disclose behavior itself. It does indicate the operation is a read ('Returns...') and adds an unusual execution-location caveat ('Runs in your Kuudo deployment, not here'). But it doesn't explain what 'Kuudo deployment' means, whether results are current, or any prerequisites, leaving important behavioral ambiguity.

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 front-loads the purpose in the final sentence, but the first two fragments—'Catalog entry.' and 'Runs in your Kuudo deployment, not here.'—are loosely structured and one is unclear. It could be tightened into a single coherent sentence.

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 parameterless listing tool, the description states what it returns and where it runs, which is close to sufficient. However, with no output schema, 'a list of inventory summaries' is vague about the response shape, and the unexplained 'Kuudo deployment' reference leaves the calling environment unclear.

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 tool has zero parameters, so the input schema is already complete (100% coverage). The description has nothing to add to parameter semantics, matching the baseline 4 for parameterless tools.

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 states a specific action and resource: 'Returns a list of inventory summaries.' This is enough to identify it as a read/list operation among the FbaInventory siblings (createInventoryItem, addInventory, deleteInventoryItem). However, the opening 'Catalog entry' is ambiguous and the description doesn't explicitly contrast it with sibling tools, so it doesn't reach a 5.

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 given about when to prefer this tool over alternatives, such as FbaInventory_addInventory or FbaInventory_createInventoryItem. The note 'Runs in your Kuudo deployment, not here' provides deployment context but does not help an agent choose this tool for a task.

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