mnemosyne_about

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

readOnlyHint already covers the non-mutating safety profile. The description adds useful behavioral context: the tool re-reads client-visible server instructions on connect and enumerates the content topic areas. It doesn't specify exact output shape, but for an informational no-parameter tool this is a minor gap rather than a serious omission.

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 efficient sentences front-load the action ('Re-read the server instructions') and then provide a compact, useful list of the contained topics plus a concrete call condition. No filler or repetition of the schema/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 a parameterless read-only about/info tool with no output schema, the description is complete: it says what the tool returns conceptually (server instruction text), what topics it covers, and when to invoke it.

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 no properties, so the zero-parameter baseline applies. There is nothing for the description to add about argument semantics, and the description doesn't invent any.

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 uses a specific verb and resource: 'Re-read the server instructions,' and then enumerates exactly what those instructions cover (governance tenet, vault protection model, spine model, memory-work rules). This clearly separates it from the operational sibling tools like mnemosyne_memory_query or mnemosyne_vault_list.

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?

It gives a concrete condition for calling: 'Most clients show this text on connect. Call it if yours did not, or to read it again.' That is an explicit when-to-use rule, and it implies the negative case (if it was already shown, no call is needed).

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