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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no info on pagination, filtering, or response shape.

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?

It is short but wastes the opening on a duplicated verb+path and a raw operation ID hash, none of which help an agent. Brevity here comes from under-specification rather than efficient front-loading.

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 tool with a nested free-form query object, 0% schema coverage, no output schema, and dozens of near-identical expense siblings, the description provides essentially nothing an agent needs to call it correctly.

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 there are 2 parameters including a free-form nested 'query' object with additionalProperties. The description gives zero information on what can go into 'query' or 'params', so it entirely fails to compensate for the schema 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 is just the HTTP method and path repeated twice ('GET /api/expenses. GET /api/expenses.'), which restates the name/title rather than explaining what is returned or how it differs from the many sibling expense tools (get_expenses_summary, get_expenses_by_lease, get_expenses_trends, etc.). An agent cannot tell which expense endpoint to pick from this text.

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 when-to-use or when-not-to-use guidance, and no mention of the numerous sibling expense tools that overlap. The only actionable pointer is 'describe_operation provides native request schemas', which is a schema-lookup hint rather than usage guidance.

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