get_registry_item

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

No annotations provided, but description discloses return value format and mentions prerequisites. It does not explicitly state read-only or side effects, but the behavior is clear from context. Could mention error conditions, but overall good.

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 short paragraphs: purpose, prerequisites/alternatives, use case and return value. Front-loaded, no wasted words.

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?

No output schema, but description explains return data in detail. Covers purpose, usage, return. Lacks error handling info, but for a simple retrieval tool it is sufficient.

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 baseline 3. The description adds meaning: 'homepage' is 'Public homepage used to generate item URL and Open-in-v0 metadata.' This goes beyond schema description.

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?

Clearly states 'Return one shadcn-native registry item generated from the current Memoire workspace.' Specific verb+resource, and distinguishes from siblings like get_specs and get_shadcn_registry.

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?

Explicitly says 'Use this tool: when an AI editor needs the exact installable context for one component or block.' Also provides prerequisites and alternatives: 'Use get_specs to list available specs or get_shadcn_registry to inspect generated item names.'

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