get_user_profile

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

Describes return data comprehensively (notification preferences, webhook, storage, etc.) but does not mention safety (read-only) or potential side effects. No annotations provided, so description partly compensates.

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 efficient sentences. First states purpose, second lists contents and usage. No redundant information.

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?

Simple tool with no params and no output schema. Description lists key return fields, providing sufficient context. Could be more complete by noting it is for the authenticated user only.

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 has 0 parameters. Description correctly adds no parameter info; baseline of 4 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?

Specific verb 'Get' and resource 'current user's detailed profile information'. Clearly distinct from sibling tools which focus on chores, labels, and circles.

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?

States 'use this to view or manage personal settings' but lacks explicit when-not or alternatives. No guidance on context where this tool is inappropriate.

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