get_profile

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

Annotations provide readOnlyHint=true, and the description adds 'SIDE EFFECTS: none' plus clarifies the scope of returned data (counts only, no listing). This supplements the annotation with useful behavioral context, though the output format is left to the output schema.

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 sentences, each carrying distinct value: purpose, usage context, and side effects. No fluff, front-loaded with the core action.

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?

The tool is simple (no params) and annotations cover safety (readOnlyHint). The description covers purpose, usage, exclusions, and side effects, making it fully self-contained 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?

With zero parameters, the description correctly avoids parameter detailing. The baseline for 0 params is 4, and the description focuses on usage semantics without conflating params with behavior.

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 states the function: 'Return the authorized account: email address plus total message/thread counts.' It uses a specific verb and resource, and distinguishes itself from siblings by explicitly noting it does not enumerate messages (use search).

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?

Provides explicit guidance: 'USE WHEN: confirming WHICH mailbox is connected before a bulk or filter action, or as a cheap liveness check.' Also gives a clear exclusion: 'DO NOT USE: to enumerate messages — this returns only counts, not a listing (use search).' This fully addresses when and when not to use the tool versus alternatives.

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