tool_get_trip_status

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

No annotations provided, but description accurately portrays a read operation with no side effects. Could mention that it does not modify data or require special permissions, but overall adequate.

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 plus arg list; front-loaded with purpose. Every sentence earns its place with no 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?

No output schema, and description only vaguely mentions 'full state + checklist progress'. For a tool with no annotations and no output schema, more detail on return format or fields would improve completeness.

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?

Adds meaning beyond schema by specifying trip_id format ('8-char') and destination when id unknown, which is helpful for correct usage. Schema coverage is 0%, so description compensates well.

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?

Description clearly states the tool retrieves a saved trip's full state and checklist progress, using specific verb 'Get' and resource. It distinguishes from siblings by specifying scope (full state + checklist) and lookup methods (id or destination).

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 lookup methods and implies use when full state is needed, but lacks explicit 'when not to use' or comparisons to alternatives like tool_get_trip_history.

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