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

No annotations are provided, so the description carries the full burden. It discloses that this is a write operation and that a receipt file is copied locally, but says nothing about required permissions, duplicate handling, what the tool returns (e.g., a new expense id), or whether the trip must already exist.

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 short sentences with no filler, and the money-format rule is stated plainly. The receipt clause ("copy an optional local receipt") is slightly awkwardly phrased and would read better as "receipt is a local file path that will be copied".

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 9-parameter mutation tool with no annotations, no output schema, and no schema coverage, the description is far too thin. It omits return value, defaults behavior, unit semantics for nights/amount, and any validation or error conditions.

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 0% across 9 parameters, so the description should compensate and does so only for two: amount ("decimal string") and receipt (optional local file to copy). Critical fields like nights, paid_by, expense_date, travel_class, and category_name receive no explanation of format or semantics beyond their titles.

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?

"Write an expense" gives a specific verb and resource, so an agent knows this creates an expense record. It does not distinguish itself from siblings like add_trip or build_claim beyond the resource noun, but the purpose is unambiguous.

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 statement of when to use this versus add_trip, build_claim, or the claim-listing tools, and no prerequisites such as whether trip_id must reference an existing trip. The agent must infer usage entirely from the name.

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

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

With no annotations, the description must carry the full behavioral burden, and it does disclose two genuinely non-obvious traits: times must be ISO-formatted and identical input reuses an existing trip rather than creating a duplicate. It still omits permissions, what happens with the defaulted fields, and what the call returns.

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?

A single compact clause pair with no filler and the key constraint front-loaded, so nothing is wasted. The terseness is efficient but tips into under-specification given eight parameters.

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 an eight-parameter write operation with no annotations, no output schema, and zero schema descriptions, two short clauses are far from sufficient. An agent can attempt a call but cannot know field semantics, defaults, or the result shape.

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 coverage is 0%, so the description is the only source of parameter meaning, yet it only constrains start_at/end_at to ISO format. Origin, destination, transport, city_tier, purpose_code, and participants are left entirely unexplained, including what values purpose_code or city_tier accept.

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 verb 'write' plus the resource 'itinerary' signals creation of a trip record, but the wording drifts from the tool name (trip vs itinerary) and never states that it registers a travel segment with origin/destination and times. It also gives no basis for distinguishing it from siblings like travel_days or add_expense.

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?

There is no guidance on when to call this versus add_expense, build_claim, or travel_days, nor any prerequisite or exclusion. The only routing-adjacent information is a reuse behavior, which is not a usage condition.

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

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

With no annotations, the description carries the full behavioral burden. It does disclose important traits such as immutability and reserving claimed items, but it omits permissions, idempotency, side effects on existing claims, and output details.

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 a single, front-loaded sentence with no wasted language. It is concise, though the brevity leaves important details unspecified.

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 mutation tool with no annotations, no output schema, and three parameters at 0% schema description coverage, the description is under-specified. It conveys core purpose but omits parameter meaning, usage guidance, and many behavioral details an agent needs.

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 0%, and the description mentions none of the three parameters: trip_ids, month, or formats. It does not compensate for the undocumented parameter semantics at all.

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 states a clear verb and resource set: writing immutable claim snapshots and local reports, plus reserving claimed items. It does not explicitly differentiate this tool from siblings such as list_pending_claims, but the core operation is identifiable.

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?

There is no guidance on when to use this tool versus alternatives like list_pending_claims or add_expense. The description gives no preconditions, exclusions, or workflow context.

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

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' weakly implies a non-mutating operation and the listed finding categories hint at the report contents, but there is no statement about scope, permissions, cost, or whether it is read-only in practice.

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?

A single efficient sentence with no filler, and the enumerated finding types are front-loaded. The phrasing 'duplicate/unmatched warnings' is slightly compressed but not wasteful.

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 must convey what comes back, and it only partly does by naming finding categories. It omits the scope of the scan and the shape of the result, leaving an agent unable to predict the response for a zero-argument call.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-related omissions exist.

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 enumerates the categories of findings (missing/orphan files, amount mismatches, duplicate/unmatched warnings), which conveys it is an anomaly-reporting tool, but the verb 'Read' is odd for a check/validation operation and the scope (which records or claims are checked) is never stated. Nothing in the text ties it to the travel/expense/claims domain implied by its siblings.

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?

There is no statement of when to run this check, what preconditions exist, or how it relates to siblings like list_pending_claims or build_claim. The agent must infer usage entirely from the name and the enumerated finding types.

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

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

No annotations are provided, so the description carries full behavioral burden. It implies a read-only operation by saying 'Read', but gives no information about permissions, return format, pagination, or whether the data is scoped to a user or organization.

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 a single efficient sentence with no wasted words and is front-loaded with the action 'Read'. It is concise, though its terseness contributes to gaps in other dimensions rather than being a structural flaw.

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 or annotations, the description should explain what the returned data looks like. It lists three return categories, which is helpful, but does not clarify format, aggregation level, or how pending claims relate to reminders and advance balances.

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 tool has zero parameters and schema coverage is 100%, so the baseline score of 4 applies. There are no parameter semantics to clarify beyond what the empty schema already communicates.

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 names three data categories it reads (reminders, unpaid amounts, advance balance) but never explicitly says it lists pending claims, leaving the resource implicit in the tool name. It is understandable in isolation but does not clearly differentiate itself from siblings like build_claim or check_missing.

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?

There is no guidance about when to use this tool versus alternatives such as check_missing or build_claim, and no prerequisites or exclusions are stated. The agent must infer usage from the name alone.

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

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

With no annotations, the description carries the full burden, and it does disclose one real trait: results are capped at one day per date. However, it says nothing about permissions, whether the read is guaranteed non-mutating, or the shape of the returned data.

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?

One tight sentence with the scope and the dedup constraint front-loaded; nothing is wasted. It is perhaps too short given the gaps elsewhere, but every word earns its place.

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?

A simple one-param read with no output schema needs only light coverage, and the cap-per-date note helps. Still, an agent cannot infer the return format (list of dates, count, objects) or what 'local-calendar' means in practice.

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 coverage is 0% for the single 'year' parameter, so the description must compensate. 'Annual' and 'local-calendar' clarify that the year is interpreted in the local calendar, but format expectations or bounds are not stated.

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 (read) and resource (annual travel days) and adds the scope qualifier 'local-calendar.' It is clear what the tool returns, though it never contrasts itself with siblings like add_trip or check_missing.

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?

Usage is implied only: the word 'annual' and the required year argument suggest fetching a year's worth of travel days. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool.

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