Codehooks.io MCP Server

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

With no annotations provided, the description carries full burden and does well: it discloses that the tool supports multiple query formats (URL-style, regex, MongoDB-style), reveals the existence of system collections like '_hooks' with metadata, and explicitly warns about dangerous operations (delete/update/replace being 'very powerful but also dangerous'). It doesn't cover rate limits, authentication needs, or pagination behavior, but provides substantial behavioral context beyond basic functionality.

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 reasonably concise (three sentences) but could be better structured. The first sentence covers core functionality, the second adds important context about system collections, and the third provides a warning. However, the warning about dangerous operations feels tacked on rather than integrated, and the description doesn't front-load the most critical information about query formats and capabilities.

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?

For a complex tool with 17 parameters, no annotations, and no output schema, the description provides adequate but incomplete coverage. It explains what the tool does and some behavioral aspects, but doesn't describe return values, error conditions, or performance characteristics. The warning about dangerous operations is valuable, but more context about mutation consequences would help. Given the complexity, the description should do more to compensate for missing structured data.

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%, so the schema already documents all 17 parameters thoroughly. The description adds some context about the '_hooks' collection and dangerous operations, but doesn't provide additional parameter semantics beyond what's in the schema descriptions. It mentions query formats generally but doesn't elaborate on parameter interactions. Baseline 3 is appropriate when schema does heavy lifting.

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's purpose: 'Query data from a collection' with specific query format support. It distinguishes from siblings by mentioning query capabilities and system collections like '_hooks', but doesn't explicitly contrast with other query-related tools (none listed in siblings). The verb+resource combination is clear, though sibling differentiation is implicit rather than explicit.

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 provides some usage context: it mentions the special '_hooks' collection for deployment metadata and warns about dangerous operations (delete/update/replace). However, it doesn't explicitly state when to use this tool versus alternatives (like 'collection' or 'export' from siblings), nor does it provide clear exclusion criteria. The guidance is helpful but incomplete for tool selection.

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