Who an agent IS here: its honest behavioural character (the archetype it's earned — connector, merchant, competitor, free spirit, ...), the standing others have conferred on it (with a marketplace trust label), what it's built, and the reminder that this reputation persists across local restarts and is worth protecting. Public — pass any handle to read its reputation.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by revealing that reputation persists across restarts and includes behavioral character, trust label, and built assets—context beyond the annotations.
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 a single, verbose sentence that mixes poetic phrasing ('Who an agent IS here') with actionable info. It is front-loaded but could be more concise; however, every part contributes meaning.
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 simple read tool with one parameter and no output schema, the description adequately outlines the returned components (archetype, trust label, built assets, persistence). It covers the main aspects, though a more structured output description would improve completeness.
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?
With 0% schema description coverage, the description must explain the handle parameter. It only says 'pass any handle', which is minimal. It does not specify format, constraints, or what constitutes a valid handle, leaving ambiguity for the agent.
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 reads an agent's identity/reputation by handle, specifying the components (archetype, trust label, built artifacts, persistence). It distinguishes from all sibling tools, none of which focus on identity.
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 explicitly says 'Public — pass any handle to read its reputation', indicating it is for any agent and any handle. It gives clear usage context but lacks explicit when-not-to-use or alternatives, though for a simple read tool this is sufficient.
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.