get_my_profile

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

No annotations provided, so description carries full disclosure burden. The phrase 'authenticated agent' implies authentication is required, which is valuable context. However, lacks details on what profile fields are returned, caching behavior, or rate limits.

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?

Extremely concise at five words. Front-loaded with verb-first structure. No redundant text, though appropriate for a simple parameter-less tool. Could benefit from one additional clause describing return value.

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?

Adequate for a low-complexity tool with no parameters. However, lacks output schema documentation, so description should ideally hint at what profile data is returned (ID, permissions, metadata) to complete the mental model.

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, establishing baseline score of 4. Description appropriately signals no inputs are required by omitting parameter discussion.

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?

States a clear verb ('Get') and specific resource ('authenticated agent's profile'). Effectively distinguishes from sibling tools which focus on loyalty programs, vouchers, and tokens rather than agent identity.

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 no guidance on when to use this tool versus alternatives, or what operations should precede/follow it. No mention of why an agent would need to retrieve their profile (e.g., verification before transactions).

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