Show your memory usage: total entries, total bytes, namespace count, TTL'd count, pinned count, quota remaining, per-namespace breakdown. Registered handle + secret required.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | ||
| secret | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds the credential requirement (registered handle + secret), which is behavioral context beyond annotations. No contradictions.
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 two sentences, front-loading the output specifics and then stating the prerequisite. Every sentence adds value, no wasted words.
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 the simple tool with no output schema, the description adequately lists all returned metrics and the credential requirement. It is missing error handling details but is sufficient for an agent to invoke.
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 0%, so description must compensate. It mentions 'handle' and 'secret' as credentials, adding meaning beyond schema's simple string type. However, it contradicts schema by implying secret is required when schema marks it optional.
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 the tool's purpose: showing memory usage with a specific list of metrics (total entries, bytes, etc.). It uses a verb and resource, distinguishing it from siblings like list_memory.
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?
The description implies usage context by stating it shows memory usage statistics and requires a registered handle and secret. However, it lacks explicit when-to-use or alternative guidance, but the purpose is clear enough to differentiate from content-oriented memory tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools serve similar purposes (e.g., web_read vs browse_read, web_discover vs browse_discover, research vs web_search + browse). Descriptions help differentiate, but the overlap is notable.
Most tools use a consistent verb_noun snake_case pattern (e.g., archive_message, browse_navigate). Minor deviations like standalone 'browse' and 'identity' are acceptable.
57 tools is very high for a single server, even with discover_tools. The broad domain coverage does not justify the count; it feels overloaded.
Covers identity, memory, browsing, human tasks, errands, messaging, and research comprehensively. Minor gaps might exist (e.g., no explicit agent-to-agent contract tools), but core workflows are well-supported.