concur_get_trip

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

Annotations already cover readOnlyHint and openWorldHint, and 'Read-only' merely restates them. What the description adds beyond the schema is the untrusted-third-party-content warning telling the agent to treat returned text as data, which is genuinely useful behavioral guidance for an open-world read.

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?

Three sentences, front-loaded with the core action and return shape, and the untrusted-data caveat placed last. The long booking-type enumeration is verbose but earns its place by telling the agent what fields to expect.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly for both header and bookings. Minor gaps remain around not-found or error behavior and whether results are paginated, but nothing essential to invoking it 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?

Schema description coverage is 100%, so the schema already fully explains tripId and the compact/full/raw view enum. The description adds no further parameter meaning, which is the expected baseline when the schema does the work.

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 ('Get one SAP Concur Travel trip') and then enumerates exactly what comes back — header fields plus flight, hotel, car, and rail booking details. This clearly separates it from the sibling list tool concur_list_trips.

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 schema note that tripId comes 'from concur_list_trips' implies the list-then-get workflow, but the description itself gives no explicit when-to-use or when-not guidance and never names an alternative tool.

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