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

No annotations are supplied, so the description carries the full disclosure burden. 'Look up' implies a non-destructive read, but the description never states what is returned (full mock definition vs. summary), how a missing/invalid slug is surfaced, or whether any auth/scope applies — meaningful gaps for an unannotated tool.

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 front-loaded sentence with no filler; the key identifier and the example appear immediately, and the clarifying benefit is stated last where it reads as a qualifier rather than preamble.

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?

The one required parameter is fully documented and the lookup key is unambiguous, but with no annotations and no output schema the description should say what the call yields (full mock object, rules, project linkage) and what happens on a slug miss. For a simple read it is callable, but the result contract 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% and the single parameter already documents the slugId format with an example ('MOCK-5cbb91d3'). The description repeats that same example rather than adding new semantics such as case sensitivity or accepted slug variants, so 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?

Specific verb ('look up') plus a singular resource ('a single mock endpoint') keyed by slugId, so the agent knows exactly what it retrieves. It does not name or contrast with the closest siblings (get_mock_detail, search_mocks, list_mocks), so the boundary between this and those tools must be inferred.

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 clause 'without needing to know project or DB ID' gives a concrete selection condition: use this when you only hold a slug. It stops short of explicitly excluding alternatives — an agent is not told to prefer get_mock_detail when a DB ID is known or search_mocks when the slug is unknown.

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