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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no pagination, filtering behavior, response shape, or auth context — and merely redirects to describe_operation.

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 body is short but the first sentence is duplicated word-for-word, which is pure waste. Brevity here comes from omission, not from disciplined front-loading of useful 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 GET endpoint with a nested undocumented query object, no output schema, and 0% parameter description coverage, an agent has almost nothing to work with beyond the path. Pointing at describe_operation offloads the entire burden rather than completing the definition.

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 schema contains a nested free-form 'query' object plus a required 'params.lineItemId' with no documented meaning. The description only echoes the lineItemId path token and never explains what the query object accepts, so it fails to compensate for the coverage gap.

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 restates the tool name/title verbatim as a REST path ('GET /api/cam/line-items/:lineItemId/expenses') with no plain-language statement of what it returns. The path implies expenses scoped to a single line item, which is marginally informative, but it is effectively a tautology of the name rather than a purpose statement.

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 the many CAM siblings (e.g. get_cam_leases_by_leaseId_ap_expenses, get_expenses_by_lease), and no mention of prerequisites or scope conditions. The only pointer is 'describe_operation provides native request schemas,' which describes a different tool, not when to select this one.

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