crystal_view

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

The description implies read-only inspection ('Inspect'), but there are no annotations (e.g., readOnlyHint) and the description does not explicitly state it has no side effects or require authorization. For an inspection tool, this is adequate but could be more explicit.

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?

Three sentences with front-loaded purpose, clear output description, and usage hint. No redundant words; every sentence adds value.

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?

Given no output schema, the description explains key return elements (patterns, lesson count, refresh time). It also mentions optional raw data. Lacks error conditions or handling of missing crystals, but covers the essential output for a simple inspection tool.

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 100%, so parameters are well-documented there. The description adds context by explaining the default output (processed) versus optional raw data, but does not provide significant extra meaning beyond the schema.

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 clearly states the tool inspects the Memory Crystal, showing top patterns per category, lesson count, and refresh time. This specific verb+resource combination distinguishes it from siblings like 'memory_crystalize' which modifies the crystal.

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 specifies to call after 'session_start' to see accumulated wisdom, providing clear timing context. However, it does not mention when not to use this tool or alternatives like 'memory_crystalize' for different needs, so guidance is limited.

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