Get shipment budget

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

The description adds value beyond annotations by specifying the return content: income rows, expense rows, totals, and logs when present. Annotations already indicate safe read-only behavior, so the description's behavioral detail is complementary and informative.

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, front-loaded sentence that efficiently conveys the core function without extraneous words. It earns its place but could be slightly improved by incorporating parameter hints.

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 lack of output schema and 0% parameter coverage, the description is incomplete. It does not explain the relationship between the two IDs (budgetId, shipmentId), the meaning of logLimit, or the default behavior of includeLogs. The tool's complexity (5 parameters) demands more detail.

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?

With 0% schema description coverage, the description provides no parameter explanations. It fails to clarify the distinction between budgetId and shipmentId, the meaning of logLimit, or the effect of includeLogs and budgetType. This is a critical gap given the parameter count of 5.

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 clearly states it retrieves a single customs or shipping shipment budget with detailed components (income rows, expense rows, totals, logs). The verb 'Get one' and resource 'customs or shipping shipment budget' are specific. However, it does not distinguish itself from sibling tools limu_get_customs_budget and limu_get_shipping_budget, which may cause confusion about when to use this versus those.

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 like limu_get_customs_budget, limu_list_shipment_budgets, or other list functions. There is no mention of prerequisites, when to use budgetId vs shipmentId, or when logs would be present.

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