edgex_get_auth_status

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool checks authentication and returns two distinct pieces of information (credential status and available tools), implying a read-only status operation. While it doesn't explicitly state 'read-only' or mention rate limits, the low-risk nature of the operation is adequately conveyed.

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 sentences long, with the core purpose front-loaded. The usage directive 'CALL THIS FIRST' is concise and impactful, and every word adds value without 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?

Given the tool's simplicity (no parameters, no output schema), the description covers the essential aspects: purpose, when to call, and the return value. It could be more specific about the output format (e.g., whether it returns a boolean or an object), but for a zero-parameter status check, this is sufficiently complete.

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?

This tool has zero parameters, and the schema coverage is 100% (vacuously), so the description needn't explain parameters. The baseline for no parameters is 4, and the description does not need to compensate for any missing parameter details.

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 'Check if authentication is configured,' using a specific verb and resource. It also mentions the return value (credential setup and available tools), making it distinguishably different from sibling getters like edgex_get_environment or edgex_get_ticker.

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 instructs 'CALL THIS FIRST at the start of every session,' providing clear when-to-use context. It implies this tool is a prerequisite for other operations, eliminating ambiguity about its role in the session flow.

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