Identify workspace

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds something annotations cannot: an explicit authorization requirement (identify:read for OAuth integrations), which is genuine behavioral context beyond the structured fields.

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 terse sentences, front-loaded with the purpose, with no filler or redundancy. It is efficient, though the extreme brevity leaves the first sentence largely redundant with the title.

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 no output schema, the description carries the burden of explaining what "identify" returns, and it does not say what account/workspace data comes back or in what shape. For a simple read tool this is a moderate gap rather than a critical one, since annotations cover the safety profile.

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?

With a single optional parameter and 100% schema description coverage, the schema fully documents the account parameter including its fallback chain (BEEHIIV_DEFAULT_ACCOUNT, first configured account). The description adds nothing further, 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?

"Identify workspace" restates the tool name and title almost verbatim; the only added substance is "Reads account data." It does not distinguish this tool from siblings like list_accounts, identify_oauth_user, or workspaces_permissions, so the agent cannot tell what "identify" actually means operationally.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer. The note about OAuth scope (identify:read) is a prerequisite, not usage guidance, so selection between this and list_accounts/identify_oauth_user is left entirely to inference.

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