mc8yp Status

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

With no annotations, description fully discloses behavioral traits: self-healing (auto-resets credentials if lost), caching of specs for 30 minutes, and the effect of `refresh: true` on cache. 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?

Description is well-structured, front-loading the main purpose and then detailing conditional behaviors. Every sentence adds value, though could be slightly more compact without losing information.

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 tool's complexity (self-healing, caching, conditional behavior), the description covers all essential aspects. No output schema, but the description sufficiently conveys that the tool returns status information. Could mention more about response structure, but not required for basic use.

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?

Single parameter `refresh` with 100% schema coverage. Description adds context beyond schema by explaining why and when to use refresh (after microservice changes) and its behavior as a noop when no tenant active. This aids in correct parameter selection.

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?

Description clearly states 'Show the current CLI status' and enumerates specific pieces of information displayed (stored tenant credentials, which tenant query/execute target, visible specs). It distinguishes from siblings (execute, query, set-active-tenant) by being a read-only status tool.

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?

Explicitly describes when to use the tool (to check status), when to use `refresh: true` (after subscribing/unsubscribing microservices), and what happens if no tenant is active (fallback to bundled snapshots, execute unavailable, need to call set-active-tenant first). Also clarifies that `refresh: true` is a noop without an active tenant.

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