alonomic_get_days_index

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

No annotations exist, so the description carries full burden. It explicitly labels the tool as 'read-only', maps to a GET endpoint, and indicates data structure. This is sufficient for basic transparency, though rate limits or auth aren't mentioned.

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?

Compact and well-organized: main English purpose, Persian translation for locale, endpoint reference, data shape, and argument docs. No wasted words, but could be slightly more structured with separate sections.

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 an output schema exists, return values need no description. The description covers purpose, data shape, endpoint, and parameters. It is largely complete for a simple read tool, though clarity on sibling differentiation is missing.

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 adds value by explaining the 'instance' parameter as 'Configured instance to use (default when omitted).' However, it remains brief and does not elaborate on instance selection or behavior beyond defaults.

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 retrieves the next 7 days with same/next-day availability, provides the API endpoint, and describes the shape of each day object as {same: bool, next: bool}. This goes beyond a simple verb+resource to include scope and data structure.

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 versus siblings like alonomic_get_days. The 'read-only' hint implies it should be used for non-mutative queries, but lacks direct comparisons or exclusions.

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