whodb_platform_workspace_resolve

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 new context: it verifies the login (an auth check with possible network failure) and explicitly does NOT mutate session/default state, which an agent needs to know before relying on it.

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 short and front-loaded with the core action, but the 'no default change' point is stated twice ('Does not switch or save defaults' then 'without changing defaults'), so one sentence is partially redundant rather than earning its place.

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, return values need not be described, and annotations cover safety. The description supplies the key precondition (optional workspace, falls back to session defaults per the schema) and the non-mutating guarantee, leaving little an agent needs that 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?

Schema description coverage is 100% with only one nested parameter, and its sub-fields (host/org/project) are fully documented in the schema. The description merely restates the same {host, org, project} triple without adding format or disambiguation detail, 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 (resolve) and resource (workspace {host, org, project}) plus the outcome (canonical IDs, login verification). The clause 'Does not switch or save defaults' cleanly separates it from siblings like whodb_platform_session_use and the discovery tools whodb_platform_hosts/orgs/projects.

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?

Explains the per-call targeting use case ('Accepts workspace {host, org, project} for per-call targeting without changing defaults') and gives an implicit when-not via 'Does not switch or save defaults'. It stops short of naming session_use or resolve_resource as explicit alternatives, but the context is clear.

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