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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description need not restate safety. It adds essentially nothing beyond announcing that describe_operation can supply native schemas, and says nothing about lookup failure behavior (missing id), response shape, or auth.

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 same route string is printed twice back to back, which is pure waste, and the content is under-specified rather than concise. The only useful clause (describe_operation provides native schemas) is buried at the end.

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 parameterized single-record GET with no output schema and zero schema descriptions, the description leaves the agent unable to predict the return payload or the meaning of the id. It is technically sufficient to construct a call from the schema alone, but adds no understanding.

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%, so the description must compensate, but it only echoes the ':id' path placeholder. The 'query' object parameter and the id's format/constraints (1-2000 chars, string) are left entirely to the schema.

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 is the raw HTTP route repeated verbatim ('GET /api/expenses/manual/:id'), which restates the tool name rather than explaining what a 'manual expense' record is or what the endpoint returns. It gives no differentiation from siblings such as get_expenses_04045e4028a17c7e5c6efb0a, get_expenses_summary, or get_recurring_expenses_by_id.

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 use this tool, when not to, or which sibling retrieves expenses differently. The only guidance is an internal pointer to describe_operation, which is about schema discovery, not tool selection.

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