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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description goes well beyond them by disclosing payload structure, that `revision_id` is a sha256 fingerprint, that `link_visibility: public` means anyone with the link can read it, and that `conventions` carries workspace conventions plus the model FINANCE.md. These are real behavioral and semantic disclosures an agent cannot get from the annotations alone.

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?

The lead sentence front-loads the return contents, followed by two short sentences covering the branch caveat and the conventions field. It is dense and field-list heavy, but every clause maps to a distinct piece of payload information an agent needs since there is no output schema.

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 carries the burden of describing the return value and does so thoroughly, including nested branch fields, the sharing roster, and the meaning of visibility values. Nothing essential for correct invocation or interpretation appears to be 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%, and the schema already explains the scoping rule for `model_id` (required for user-scoped keys, validated against the bound model for model-scoped keys). The description adds nothing about the parameter, which is acceptable given full coverage but earns only the baseline.

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 opens with a specific verb and resource ('Returns the full detail of a model') and then enumerates the concrete payload: items, lists, timelines, formats, number_locale, glyph, revision_id, version_number, branches[], and sharing. It also differentiates itself from the sibling `layerz_read` by noting this is the fuller payload versus a filtered snapshot.

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?

It gives a clear selection cue against `layerz_read` (larger payload, full detail vs. filtered snapshot) and clarifies that item values are the base plan while branch values require `layerz_read` with `branch_id`. It stops short of an explicit 'use this when you need X, not Y' statement, so it is strong context rather than a full routing rule.

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