get_profile

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds value beyond that by disclosing the return surface (theme, custom links, verification display settings) and a concrete auth prerequisite with a remediation step. It does not mention pagination or error behavior, but for a single-record read that is minor.

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-loaded with purpose and return contents, then a clearly separated ACCESS block. Slightly verbose for the amount of information conveyed, but every sentence is actionable and nothing is filler.

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 appropriately summarizes the return payload, and it covers the non-obvious auth barrier that would otherwise cause a failed call. Only the relationship to closely named siblings (list_profiles, get_my_profile) is left unaddressed.

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 description coverage is 100% for the single profile_id parameter, so the schema does the documentation work. The description only echoes 'by ID' and adds no format, source, or lookup guidance, putting it at the baseline for a fully-covered schema.

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 a specific profile by ID') and enumerates what the response contains. It implicitly separates itself from the plural list_profiles, but never names siblings like get_my_profile or get_profile_assets, so an agent must infer which 'get profile' variant applies.

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?

Usage context is implied by 'by ID' and there is a genuine negative hint ('start_login does NOT open this tool'), but the text is dominated by credential setup rather than when-to-choose-this-tool. No guidance on where to obtain a profile_id or when to prefer get_my_profile.

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