SupplySources_getSupplySource

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

With no annotations, the description carries the behavioral disclosure burden. It does add useful context by stating that execution occurs 'in your Kuudo deployment, not here' and implies a read-only operation with 'Retrieve.' However, it does not disclose authentication needs, error behavior, or what 'catalog entry' means operationally, leaving meaningful gaps.

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 wastes few words. The environmental note and the retrieval purpose are both present. However, the opening 'Catalog entry.' is fragmented and jargon-like, reducing structural polish without adding much 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?

The description is too sparse for a tool with no annotations and no output schema. It explains where the tool runs but not how to identify which supply source to retrieve, what the response contains, or what prerequisites exist. Given the singular 'getSupplySource' name and empty schema, an agent would not know how to invoke it correctly in a non-trivial context.

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 declared properties and additionalProperties is true, so there are no parameters for the description to document. Per the 0-parameter baseline, this is acceptable. The ambiguity of additionalProperties true is not clarified, but the description cannot add much parameter meaning when none are declared.

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 verb and resource: 'Retrieve a supply source.' This is clear enough to know the basic operation. However, 'Catalog entry' is vague and does not distinguish this from the sibling SupplySources_getSupplySources, so it misses explicit 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 use this tool versus alternatives. The phrase 'Runs in your Kuudo deployment, not here' hints at environment context but does not explain when this should be selected over SupplySources_getSupplySources or other SupplySources tools. No exclusions or alternative routing are provided.

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