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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond that: any role may read, and a missing document returns exists/data with data null rather than erroring, which materially affects error handling.

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?

Two sentences, zero filler, and the path-mode distinction is front-loaded immediately after the purpose statement. The return-shape notation is dense but readable.

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 correctly spends its space documenting return shapes for both the document and collection cases. The one meaningful gap is the unexplained `id` parameter relative to a 0% documented schema.

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 coverage is 0%, so the description carries the burden. It does clarify that `path` encodes either 'collection/docId' or a collection, which is the key semantic distinction, but the required `id` parameter is never explained (presumably the artifact id) and no format or validation hints are given.

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 ('Read the artifact's shared database') and immediately characterizes the two path modes. It does not differentiate from the closely related sibling db_query, so an agent must infer the split between a keyed get and a query.

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?

Usage is implied by the two path forms and the '(any role can read)' permission note, which is genuinely useful. However, there is no explicit statement of when to prefer this over db_query or db_set/db_delete siblings, nor any prerequisite or exclusion.

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