get_my_profile

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

readOnlyHint=true already covers the safety profile, so the bar is lower. The description adds genuine value by disclosing the return envelope (theme, custom links, public proof display settings) and the account/auth prerequisite, plus the non-obvious note that start_login does NOT unlock this tool.

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?

Front-loads the purpose, then separates the ACCESS prerequisite into its own labeled block. Every sentence carries information; the only mild slack is that the return-value list could conceivably be trimmed given how generic it is.

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?

With no output schema, the description usefully enumerates the returned data and flags the auth prerequisite, which is exactly what a 0-param read tool needs. The one gap is the absence of any sibling routing (get_profile vs get_current_user), which keeps it short of fully complete.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool is 4. No wording misleads about inputs.

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 specific verb and resource ('Get the current user's primary profile') and enumerates the returned data (profile details, theme, custom links, proof display settings). The 'my/primary' framing implicitly distinguishes it from get_profile and list_profiles, but it never names those siblings explicitly.

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?

The ACCESS block gives real operational guidance on preconditions (needs a Proof account, set PROOF_API_KEY, restart), which is useful. However, it offers no routing versus adjacent tools like get_profile, get_current_user, or list_profiles, so when-to-use-which is left to inference.

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