get_current_user

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful context beyond annotations by stating credentials and tokens are excluded from the profile, which informs agents about data scope. No contradiction.

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?

Two short sentences, front-loaded with the action and resource. The exclusion note earns its place by adding data-scope clarity without fluff.

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?

For a zero-parameter, read-only tool with annotations covering safety and idempotence, the description covers what it returns (profile) and what it excludes (credentials/tokens). No output schema exists, but the tool's simplicity means the agent can call it safely and inspect the result. Complete enough.

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?

Tool has zero parameters and schema description coverage is 100%. Description adds no parameter details because none are needed; baseline for zero parameters is 4.

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?

Description states specific verb 'Read' and resource 'logged-in RENPHO Health account profile', and clarifies that credentials/tokens are excluded. This clearly distinguishes it from siblings like get_scale_users (different resource) and refresh_session (session/token operation).

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 clear context for when to use: retrieving the current logged-in account profile. It does not explicitly name alternatives or state when not to use it, but the exclusion of credentials/tokens signals it is not for auth-sensitive data. Clear context without explicit exclusions.

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