razz-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It omits critical information: whether the operation is read-only, what data structure is returned, pagination behavior, or rate limits. It only describes the search scope.

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 a single 11-word sentence that is front-loaded with the action verb and efficiently conveys the core function. However, the extreme brevity is insufficient given the lack of annotations and output schema.

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 complete parameter schema coverage (100%), the input requirements are documented. However, given the absence of annotations and output schema, the description inadequately discloses the return format or read-only safety properties necessary for confident agent invocation.

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%, establishing a baseline score. The description mentions 'current room' and 'accessible rooms' which aligns with the roomId parameter's default behavior, but this largely restates the schema description without adding significant semantic depth or format examples.

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 provides a specific verb ('Search') and resource ('messages'), and clarifies scope ('current room or across all accessible rooms'). It implicitly distinguishes from siblings like razz_read_messages (retrieval without query) and razz_send_message (creation).

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 description states the functional scope (current vs all rooms) but provides no explicit guidance on when to use this tool versus alternatives like razz_read_messages, nor does it mention prerequisites or exclusion criteria.

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