monnet_whoami

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions verifying the connection and listing API keys, which implies read-only behavior and possible exposure of sensitive data, but it does not explicitly state that no modifications occur or describe what happens on failure. More detail could improve 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 two short sentences, front-loaded with actionable verbs. Every word contributes meaning: 'Verify', 'list', 'debugging setup issues'. There is no waste or redundancy.

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 zero-parameter diagnostic tool with no output schema, the description is remarkably complete. It states the purpose, the specific actions, and the ideal use case. No further details are necessary for an agent to decide when and how 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 tool has zero parameters, so the baseline is 4. The description correctly avoids mentioning parameters, and the input schema (empty properties) aligns with the described functionality. No additional parameter semantics are needed.

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 two specific verbs: 'Verify your Monnet MCP connection' and 'list the API keys on your account', which clearly identifies the tool as an identity/connection check. This distinguishes it from siblings like list_workspaces and get_motion, which operate on different resources.

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 states 'Useful for debugging setup issues', giving a clear scenario for when to use the tool. While it doesn't explicitly exclude alternatives or mention when not to use it, the context is sufficient for a diagnostic tool of this nature.

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