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

The description states it is an inspect/read operation, aligning with the readOnlyHint annotation. It discloses what each view returns (references or versions with content), adding context beyond the annotation's simple read-only flag. No destructive behavior is implied, consistent with the lack of a destructiveHint.

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 description is two sentences and largely to the point. It packs a lot of detail into a semicolon-separated list, which slightly reduces readability, but remains efficient and well-structured.

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 explains the return content for each view, which is sufficient for a simple two-parameter tool. It lacks explicit mention of error cases or pagination, but these are not critical for basic usage and the description covers essential behavior.

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?

The schema already covers both parameters with descriptions and a default. The tool description adds meaning by explaining what the 'used_by' view lists (mock rules, test cases, seeds, doc examples) and what 'versions' returns (saved versions with content), going beyond the schema's terse descriptions.

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 uses a specific verb ('Inspect') and identifies the resource ('project fixture') with two distinct views ('used_by' and 'versions'), clearly differentiating it from sibling tools like get_fixture (which likely returns fixture details) and list_fixtures.

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 provides clear when-to-use guidance: 'used_by' is for checking before changing or deleting a fixture, and 'versions' is for viewing saved versions. Also notes the prerequisite 'Requires project context.' However, it does not explicitly name alternative tools to compare against.

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