alonomic_get_parcel_sizes

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

No annotations provided, so description carries full burden. It states the tool is read-only and lists sizes, but does not disclose authentication needs, rate limits, error behaviors, or what happens if the instance parameter is omitted. Minimal disclosure beyond the obvious.

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?

Description is concise: 6 lines covering purpose, Persian translation, API mapping, and parameter explanation. No unnecessary words, but the structure could be improved by grouping related information. Still, it is well within acceptable length.

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 tool's simplicity (one optional parameter, read-only list), the description is mostly complete. It specifies the number of items (12) and dimensions. The existence of an output schema reduces the need to detail return values. Brief but adequate for basic usage.

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?

Schema coverage is 0%, so description must add meaning. It explains the 'instance' parameter as a configured instance to use, with a default when omitted. This provides some context beyond the schema, but is brief and does not elaborate on how the instance is used or what constitutes a valid instance.

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?

Clearly states it lists standard parcel box sizes and is read-only. Specifies the API endpoint and mentions it returns 12 box sizes with dimensions. Distinguishes from sibling tools like create/update/cancel by being read-only.

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 explicit guidance on when to use this tool vs alternatives. Only mentions it is read-only, but does not state when to choose it over other parcel-related tools. Lacks when-not-to-use or alternative references.

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