lazymac-mcp

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

No annotations are provided, so the description carries full burden. It lists operations but doesn't disclose behavioral traits like whether these are read-only or mutating operations, authentication needs, rate limits, or output formats. For a tool with potentially complex text processing, this is inadequate.

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 extremely concise—four brief phrases separated by commas—with zero wasted words. It's front-loaded with the core functions and efficiently communicates the scope in minimal space.

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 annotations, no output schema, and a generic input schema, the description is incomplete. It lists functions but doesn't explain how they work, what inputs they expect, or what outputs they produce. For a tool with potentially multiple operations and complex text processing, this leaves too much undefined.

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 input schema has 1 parameter with 100% description coverage, but the schema description is generic ('Free-form params object'). The tool description doesn't add any parameter-specific semantics, but with 0 required parameters and high schema coverage, the baseline is 3. Since it's a single free-form parameter, a score of 4 reflects that minimal parameter documentation is acceptable.

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 lists four functions (Markdown ↔ HTML, TOC extraction, link extraction, linting) which gives a general idea of capabilities, but it's vague about the specific verb+resource combinations and doesn't distinguish this tool from potential siblings. It mentions multiple operations without clarifying if it's a single multi-function tool or separate tools.

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?

No guidance is provided on when to use this tool versus alternatives. The description lists functions but doesn't specify contexts, prerequisites, or exclusions. Given the sibling tools include text_analysis and other text-processing tools, this lack of differentiation is a significant gap.

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