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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), so the description's value lies in disclosing what comes back — tool inventory, auth requirements, replacement mappings, and data provenance. That return-content framing is genuinely useful given there is no output schema, though it says nothing about cost, size, or freshness of that metadata.

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?

A single front-loaded sentence with a colon-delimited list of exactly what is exposed — zero filler, no restatement of the title, and every clause carries distinct information.

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?

With no input parameters and no output schema, the description carries the burden of telling the agent what it receives, and it does so with four concrete content categories. It is complete for a simple discovery tool, with only minor gaps around when in a workflow it should be called.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The empty schema matches the parameterless contract described implicitly by the tool.

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?

States a clear verb+resource (describe this MCP server) and enumerates the specific payload: tools, free vs sign-in status, what each replaces, and data provenance. It does not explicitly distinguish itself from siblings like mzizi_get_architecture or mzizi_get_doctrine, so an agent must infer that this is the broad, meta-level overview rather than a topic-specific lookup.

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?

Usage is implied rather than stated: the enumeration of server-wide metadata suggests this is a discovery/first-call tool, but there is no explicit when-to-use, when-not, or named alternative among the many sibling tools. An agent can infer intent, but nothing routes it definitively.

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