Get account profile

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

With readOnlyHint=true and openWorldHint=false, annotations already establish the read-only safety profile. The description adds meaningful behavioral context by detailing the returned capability matrix, numeric limits, and active workspace, and how this supports pre-checking feature gates and confirming publish context. No contradictions.

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 information-dense but each clause adds value: profile fields, entitlements, limits, workspace, and usage rationale. It is front-loaded with the primary resource and avoids filler, though the first sentence is somewhat long and parenthetical.

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 zero parameters, a readOnly annotation, and the presence of an output schema, the description fully covers the tool's purpose, content, and when to invoke it. It explains both the account profile and workspace aspects, leaving no significant gaps for 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?

There are zero parameters and schema coverage is 100%, so the description need not explain parameters. Per the rubric, 0 params yields a baseline of 4; the description focuses on output semantics, which is appropriate.

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 specifies the resource (authenticated account profile) and the exact contents returned: profile fields, entitlements, numeric limits, and active workspace. It distinguishes from sibling tools by emphasizing the combined payload for feature gating and pre-publish workspace confirmation, something no single sibling provides.

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 gives explicit usage context: call before a multi-team publish to confirm workspace, and for feature gate pre-checks to avoid separate lookups. It does not name alternative tools like dropthis_workspaces, but the 'no separate lookup' phrasing implies when not to use other tools.

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