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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation, what the returned 'copy and checks' means, whether there are side effects, or what the response format is. The phrase 'copy and checks' is too unclear to infer even a basic behavior.

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 short, but the brevity comes at the cost of clarity. The opening phrase 'Copy and checks' is confusing and not front-loaded with a clear action. It is under-specified rather than efficiently concise.

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?

This is a simple one-parameter tool, but the description is still inadequate. It does not explain the purpose clearly, lacks behavioral context, and provides no details about the output or how it differs from sibling tools. An agent cannot reliably invoke this tool based on the description alone.

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 already documents slug as 'tool slug' with 100% coverage. The description adds a concrete example, 'title-tag-checker', which helps clarify the expected format. However, it does not add much more semantic value beyond what the schema provides.

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 mentions a resource (micro-tool) and an identifier (slug), but the phrase 'Copy and checks' is grammatically ambiguous and does not clearly convey the action of retrieving or getting a tool. It is not a clear verb+resource statement and may mislead the agent about whether this tool copies or checks something.

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 when-to-use guidance is provided. The phrase 'by slug' implies this tool is for looking up a single micro-tool, and the example hints at an identifier, but there is no explicit context about when to prefer it over siblings like list_tools. No alternative tools or exclusions are mentioned.

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