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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add what they do not: results are grouped by job, every reply carries explain and next, and errors return a structured {error, field, got, reason, fix}. That is genuinely useful runtime behavior. It does not indicate response size or whether the full catalog can be truncated, which is a notable omission for an all-tools index.

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?

It is a compact definition with the when-to-use clause in the first clause and the alternative-routing information immediately after. The job list is long but earns its place by letting an agent predict whether its task is covered without calling the tool. A slightly dense read, but nothing is redundant with the schema or annotations.

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 an index/meta tool with one optional parameter and no output schema, the description covers what is returned (tools grouped by job), the auxiliary reply fields (explain, next), the error contract, and the pointer to the full list URL. Only the discovery-to-invocation mechanics remain slightly under-specified.

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 coverage is 100%, so the single optional topic parameter is already documented with group examples and the 'problems' special case. The description reinforces 'problems' but adds no new semantics such as matching behavior for unknown topics or whether values are case-sensitive. Baseline 3 is appropriate where the schema does the work.

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 states a specific behavior: it returns every other MIZAN tool grouped by job, with each callable at the same address. It also distinguishes itself from siblings by naming check, require, prove and claim_identity as the things it is not. The list of jobs it covers (credential verification, standard/gates, public log, identifier linking, agreements, counterparty watching) clarifies scope, though it reads as a run-on enumeration rather than a crisp purpose statement.

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?

Explicit routing guidance is given: call this when check, require, prove and claim_identity are not the job, and use more("problems") to get the problems MIZAN solves. What is missing is guidance on how to move from a discovered group to the actual call – 'each is callable at this same address' is ambiguous about whether that means this endpoint or a separate per-tool dispatch.

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