orders_after_date

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

Since no annotations are provided, the description carries the full burden of disclosing behavior. It explicitly states that filtering is done locally (a key implementation detail) and that the return is a dict containing filtered orders or error information. This adds meaningful behavior beyond what a static schema would reveal, though it could mention performance implications of fetching all orders first.

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 extremely concise and well-structured. It opens with the core purpose, includes a brief note on filtering behavior, and then clearly lists arguments and returns. Every sentence adds value without redundancy.

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?

For a simple one-parameter tool with an output schema, the description covers the input format, return type, and filtering behavior. It could specify whether 'after' includes the given date, but this is a minor gap and not essential for correct 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?

The schema only defines 'date' as a string with no description. The tool's description adds critical format information (YYYY-MM-DD) in the Args section, which is essential for correct invocation. This compensates well for the low schema coverage.

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 'Retrieve all orders after a given date (YYYY-MM-DD)' with a specific verb, resource, and scope. It distinguishes itself from siblings like orders_between_dates (range) and get_all_orders (no filter) by emphasizing the date-based filtering.

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 note 'This filters locally since the GraphQL schema doesn't have date filters' provides helpful context on why this tool exists and when to use it. However, it does not explicitly mention alternatives like orders_between_dates for range queries or when not to use this tool.

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