Get current organization (auth check)

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

Annotations already declare readOnlyHint true, destructiveHint false, idempotentHint true. Description adds context that this is an auth check returning organization name, and shows the return structure. It explains the output format parameter. No contradictions; adds value beyond annotations.

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?

Four short sentences covering purpose, usage, return value, and two examples. No fluff; every sentence serves a purpose. Well-structured for quick comprehension.

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 simple auth check tool with one optional parameter and no output schema, the description is fully complete. It explains when to use, what it returns, and provides examples. No missing context needed by an AI agent.

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 100% with a single parameter (response_format) already described in schema. The description does not elaborate on parameter behavior beyond the schema, but provides example usage. Baseline 3 is appropriate as schema carries the semantic load.

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?

Specifically states 'Verify the configured API key works and return the organization name.' This clearly identifies the verb (verify/return) and resource (API key/organization name). The title 'Get current organization (auth check)' and description differentiate it from sibling tools like kanbanzone_get_organization, which likely provides more detailed organization info.

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 guides usage: 'Use this first when troubleshooting setup — if it returns the org name, auth is working.' This tells when to use (setup troubleshooting) and implies alternatives (other tools for organization details). Provides clear context for selection.

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