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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful value by disclosing the shape of the returned record (client, stage, billing settings, balances, custom fields), but says nothing about behavior on a missing/invalid UUID or about the freshness of live external data implied by openWorldHint.

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 sentence with zero filler; the unique-key qualifier ('one matter by UUID') is front-loaded and the payload listing follows. Nothing could be cut without losing information.

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 one-parameter read-only fetch with no output schema, the description carries the important part: what the returned record contains. Annotations cover safety, and the remaining gap (error behavior for unknown UUIDs) is minor for this tool class.

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 0% for the single required parameter, so the description must compensate; 'by UUID' does clarify that matter_uuid is a UUID identifier rather than a numeric id or slug. It does not state where to obtain that UUID, which is the one piece of semantic guidance missing.

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 noun phrase 'one matter by UUID' plus the enumerated payload (client, workflow stage, billing settings, balances, custom fields) makes clear this is a single-matter fetch, implicitly contrasted with lawcus_list_matters. The verb itself is carried only by the name/title, so it is clear but not maximally explicit.

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 'by UUID' phrasing implies the prerequisite that the agent must already hold a matter identifier (from lawcus_list_matters or lawcus_search), which is the only usage signal. There is no explicit when/when-not statement, no naming of alternatives, and nothing about resolution when the UUID is unknown.

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