mesh_profile

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

No annotations provided, so description carries the burden. It states the profile is 'all ledger-derived,' implying read-only access and blockchain-based data. However, it does not disclose potential side effects, authorization requirements, or data freshness. For a read operation, this provides moderate transparency.

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, informative sentence. It front-loads the key purpose and enumerates returned data fields. While compact, it lacks structured details such as separate sections or examples, but remains efficient.

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 one parameter and no output schema, the description sufficiently explains the tool's return (specific fields: sells, reliability, followers, regulars, earnings). It covers the essential context for a simple retrieval tool, though the agent might benefit from more detail on the handle parameter's source.

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 add meaning. The description mentions 'A node's public MeshVibe profile,' implying the required 'handle' parameter identifies a node. This adds context beyond the raw schema but does not specify format or constraints (e.g., string length).

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 retrieves a node's public MeshVibe profile with specific fields (sells, reliability, followers, etc.). While it lacks an explicit verb like 'get' or 'retrieve', the noun phrase 'A node's public MeshVibe profile' effectively conveys the resource and scope. It distinguishes from sibling tools like mesh_signup (registration) and mesh_publish (publishing).

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?

No guidance on when to use this tool versus alternatives. Among many sibling tools (mesh_signup, mesh_discover, etc.), there is no mention of contexts where mesh_profile is appropriate or where other tools might be better. The agent must infer usage from the name alone.

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