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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description's 'idempotent' is partly redundant. However, it adds real value beyond the annotations by scoping the mutation ('Only changes the read flag') and disclosing an auth requirement ('Requires a wallet signature identity'), neither of which appears in structured fields.

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?

One front-loaded sentence carries purpose and both modes, followed by two short clauses for id sourcing and side effects. No filler, and the most important fact (scope of the mutation) comes first.

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 only one optional parameter, full schema coverage, annotations covering safety/idempotency, and an output schema handling return values, the description covers everything an agent needs: what it does, where ids come from, side-effect scope, and auth requirement.

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% and the single optional `id` is already documented, including the omit-means-all behavior. The description restates that rather than adding format or constraint detail (e.g., the 24-hex ObjectId pattern), so it meets the baseline but does not exceed it.

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+resource ('Mark ... notifications as read') and explicitly covers both modes: single by `id`, or all when `id` is omitted. Nothing in the sibling list does anything similar, so the tool is instantly distinguishable from tools like `tronsave_list_notifications`.

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?

Gives the precondition for the argument ('Get ids from `tronsave_list_notifications`') and the condition that selects each mode (with `id` vs. omitted). That is an explicit routing rule to the sibling that supplies the input.

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