get_own_profile

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

Labels tool as 'Read-only', a key behavioral trait. Lists exact keys returned. No annotations provided, so description carries full burden, but could mention any rate limits or side effects; however, for a read-only profile retrieval, the description is sufficient.

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?

Description is succinct (4 sentences) with important information front-loaded: 'Read-only' and 'Return the authenticated user's full profile...'. Every sentence adds value with no redundancy.

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 the tool's simplicity (no parameters, no output schema), the description fully explains purpose, when to use, what it returns (including key names), and how it differs from a sibling. Complete context for selection and invocation.

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?

Input schema has zero parameters and schema description coverage is 100%. Baseline is 4. Description explicitly states 'No args', consistent with schema, adding no new information but confirming 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?

Directly states the tool returns the authenticated user's profile as a dict with specific keys. Clearly distinguishes from sibling get_profile by specifying alternative for other users.

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?

Explicitly describes when to use ('who am I' calls, preflight checks) and when not to (for other user profiles, use get_profile). Provides context for auth handle needed for WRITE tools.

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