SupplySources_getSupplySources

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

With no annotations, the description carries the burden. It does add useful behavioral context: the operation runs in a separate Kuudo deployment and returns paginated data. It does not disclose auth requirements, rate limits, or a clear read-only statement, but 'retrieve' and pagination imply a read operation.

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 compact and front-loads the key facts: catalog entry, execution location, and paginated retrieval. 'Catalog entry' adds limited value, but there is no redundancy or unnecessary detail.

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 read/list tool, the core is present, but the lack of an output schema or annotations leaves return format and authorization expectations implicit. The 'Catalog entry' phrase also introduces ambiguity about whether this is directly invocable, which is not resolved.

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 has zero parameters with 100% coverage, so the baseline is 4. The description's pagination mention is the only parameter-related hint and confirms the list nature, but there are no parameter semantics to clarify.

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 concrete action ('retrieve') on a specific resource ('supply sources') and indicates pagination, which distinguishes it from the singular getSupplySource and the create/update/archive siblings. However, the opening 'Catalog entry' is ambiguous and no sibling is named, so it stops short of full differentiation.

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 choose this tool over SupplySources_getSupplySource (single vs. paginated list) or the write operations. The only contextual statement, 'Runs in your Kuudo deployment, not here,' addresses runtime location, not tool selection.

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