alonomic_get_days

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

With no annotations, the description notes the tool is read-only and maps to a GET endpoint, providing basic behavioral context. However, it omits details about rate limits, error handling, or any constraints on the data returned.

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 concise and front-loaded with the main purpose. The inclusion of a Persian translation is extra but not harmful. The structure is clear and efficient, though the Persian line is redundant for English agents.

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 has one optional parameter and an output schema, the description covers the essential information: purpose, param, and read-only nature. It does not describe the output format, but the output schema compensates. Overall adequate for a simple tool.

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 parameter 'instance' is briefly explained as 'Configured instance to use (default when omitted)', which adds some meaning beyond the schema's type definition. However, with 0% schema description coverage and only one parameter, a more detailed explanation of 'instance' values or defaults would improve clarity.

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 gets working pickup days for today/tomorrow and specifies it is read-only. It also provides the API endpoint, distinguishing it from siblings like 'alonomic_get_days_index' which likely serves a different purpose.

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?

The description implies usage for retrieving current and next day's pickup slots but does not explicitly state when to use this tool versus alternatives like 'alonomic_get_days_index' or other scheduling tools. No exclusions or context are provided.

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