whodb_platform_status

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the hosted-login prerequisite and the fact that passing a workspace targets a single call without mutating session defaults.

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?

Three tight sentences with the core purpose front-loaded, then prerequisite, then usage. The final sentence duplicates what the schema already says about per-call targeting, which is minor waste but not harmful.

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?

With an output schema present, annotations covering the safety profile, and 100% parameter coverage, the description supplies everything else an agent needs: what it reports, the login prerequisite, and when to call it relative to other platform tools.

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 description coverage is 100% and the nested workspace object (host/org/project) is fully documented in the schema, including default-resolution behavior. The description largely restates that ('for per-call targeting without changing defaults'), so the baseline 3 applies.

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?

States a specific verb and resource ('Report the current hosted WhoDB login and selected hosted workspace') and clearly separates this read-only status check from sibling tools like whodb_platform_session_use and whodb_platform_hosts/orgs/projects. An agent can identify its role without opening any schema.

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?

Gives explicit when-to-use guidance ('Use this before other whodb_platform_* tools to confirm which host, organization, and project are active') and a prerequisite ('Requires a prior hosted login with whodb login'). It does not name a when-not condition or explicitly route the agent to session_use/hosts as alternatives in the description text, so it stops short of a 5.

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