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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the meaningful context that the profile must be linked/connected and that it returns the current account's profile data, which is useful but not extensive.

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?

The description is a single tight sentence with no filler or redundancy. The key content (what account and what fields) is front-loaded, and the prerequisite is clearly appended.

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?

For a zero-parameter, read-only profile retrieval tool, the description is largely complete: it names the resource, lists the returned fields, and states the connection requirement. The lack of an output schema is partially compensated by the field list, though behavior when no account is connected is left implicit.

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?

There are zero parameters, so the baseline is 4. The description's mention of returned fields (name, email, SmartSites handle/bio) is output-oriented, not parameter-related, and adds no parameter semantics, but no parameters exist to document.

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?

The description clearly identifies the resource (the linked Swop account) and the returned data (name, email, SmartSites), which matches the 'Get my profile' title. It is not a tautology and is distinguishable from identity-related siblings by the 'my' scoping, though it does not explicitly name any sibling.

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 description implies this tool is for the caller's own connected Swop profile and states a prerequisite ('Requires connecting your Swop account'). However, it provides no explicit guidance on when to choose this over alternatives like swop_lookup_identity or swop_search_identities.

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