invariance_agent_me

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

The readOnlyHint annotation already declares the non-mutating nature, and the description adds what the tool returns: the agent identity and API key. This disclosure is meaningful and consistent with the annotations, though it could add a note about the sensitive nature of the API key.

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 compact, front-loaded sentences: the first gives the action and result, the second gives the practical reason to call the tool. No filler or redundant detail.

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 introspection tool with no output schema, the description covers both the result of invocation and the intended benefit. It stops short of spelling out the exact output shape, but nothing required for correct invocation is missing.

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 is an empty object, meaning there are no parameters and 100% schema coverage. With zero parameters, the baseline of 4 applies, and there is simply nothing further for the description to explain.

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 states a specific action ('Show') and resource ('agent identity and API key') bound to the current credentials. This clearly distinguishes it from the many agent-related siblings such as invariance_agent_get and invariance_agent_list, which address other agents.

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 second sentence provides an explicit use case: confirming the agent context under which the MCP server operates. It does not reference alternative tools or exclusions, but the purpose of this parameterless introspection tool is unambiguous.

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