List active orders at a location

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive behavior. The description adds the login requirement ('Requires craveup login') and the data-source equivalence with the Orders Manager, which are useful behavioral details beyond the annotations.

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?

Two concise sentences with no wasted words. The main operation and scope are front-loaded, and the auth prerequisite earns its place as essential usage information.

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 read-only list tool with an output schema, safety annotations, and fully described parameters, the description covers the operation, scope, data source, and auth requirement. Nothing essential is missing for an agent to invoke it correctly.

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 single parameter locationId is fully described in the schema, including the default behavior when omitted ('Omit to use CRAVEUP_LOCATION_ID'). With 100% schema coverage, the baseline of 3 applies; the description adds no additional parameter-level detail.

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?

States a specific verb and resource: 'Fetch active (new) orders for a location,' reinforced by the title 'List active orders at a location.' The phrase 'same data as the Orders Manager' adds clarity and helps distinguish it from the many setup/management sibling tools.

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?

Provides clear context for when to use the tool: retrieving active orders for a location, and notes the login prerequisite. It does not name explicit alternatives or exclusions, but no sibling tool serves the same order-fetching purpose, so the guidance is sufficient.

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