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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context beyond the annotations: results can be truncated and how to react, plus the no-confident-match fallback of omitting categoryId. It does not describe the return shape, but the truncation and matching semantics are the important behavioral facts here.

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?

Three sentences, each front-loaded and load-bearing: purpose, then use-case plus fallback, then truncation handling. No filler or restated structured data.

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 single-optional-param read tool with annotations covering safety and no output schema, the description covers purpose, resolution workflow, and both edge cases (no match, truncation). Nothing material to correct invocation is missing.

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 100%, so the schema already defines nameLike as a case-insensitive substring filter. The description reinforces this indirectly ('more specific nameLike') when discussing retries but adds no format, syntax, or semantic detail beyond the schema. Baseline 3 applies.

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 and resource ('List the user's transaction categories') and no sibling tool returns categories, so it is unambiguous against get_accounts, get_assets, etc. The description also frames the resource's purpose (categoryId resolution), which sharpens what the list is for.

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?

Explicitly names the trigger ('before proposing a transaction or asset trade') and the direct consumers (propose_transaction, propose_asset_trade). It further covers two edge cases: omitting categoryId on no confident match, and re-calling with a narrower nameLike on truncation, which is exactly the when/when-not guidance an agent needs.

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