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 fully covered. The description usefully adds that it aggregates current-year and all-time totals, open items, and payment timing, but says nothing about auth scope, result size, or behavior for an unknown name_or_id.

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 front-loaded sentence that leads with the scope ('Everything about one customer or vendor') then lists the data included. Dense but every clause carries retrieval-relevant content, with no filler.

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 does the heavy lifting on returns and covers them well (totals, open invoices/bills, last payments, average days to pay). However it never addresses the required identifier parameter or the company scoping behavior, which 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?

Based on the description alone, no parameter is explained; the schema documents only 'company' (50% coverage). The required 'name_or_id' has no schema description and no mention in the description, leaving the most important input's accepted forms (exact name? id format? fuzzy match?) unspecified.

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 (get) and resource (one customer or vendor profile) and enumerates the returned content, so an agent knows exactly what the tool produces. It does not name or contrast any sibling such as query_invoices or get_activity, so it stops shy of a 5 despite the clear resource.

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 scope phrase 'one customer or vendor' implies this is the per-counterparty aggregate lookup, which is implied usage guidance. There is no explicit when-to-use trigger or named alternative (e.g., query_invoices for line-level detail), so it does not reach the 4-5 tier.

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