mockzilla_docs_topics

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

No annotations provided, but the description is self-sufficient: it describes a read-only listing operation with no side effects. It does not contradict any annotations. The behavior is obvious from the description.

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?

Two sentences: first states the purpose with examples, second provides usage guidance. No wasted words. Front-loaded and efficient.

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 parameters and no output schema, the description fully covers what the tool does, when to use it, and how it relates to siblings. No missing information.

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 0 parameters with 100% coverage (empty). The description adds meaning beyond the schema by explaining the purpose, examples, and contextual usage. Baseline for 0 params is 4, and the description meets it well.

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 it lists available mockzilla doc topics with examples (e.g., 'usage/portable', 'middleware'), and distinguishes it from sibling tools by explaining when to use each (search and read).

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 states to call once at the start of a session involving non-trivial mockzilla usage, and then suggests calling `mockzilla_docs_search` or `mockzilla_docs_read` for specific topics. Provides clear when-to-use and next steps.

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