get_my_profile

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

No annotations provided, so the description carries the burden. It states the tool opens a browser/navigation to the profile page, which implies a browser context (consistent with siblings like navigate, close_browser). However, it doesn't clarify what 'visible profile text' includes (e.g., only what's currently visible vs. full text), scraping reliability, rate limits, or whether login is required before use.

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?

A single concise sentence with no wasted words. Efficient and front-loaded. Could arguably add one more sentence of usage context without becoming verbose, but as-is it's appropriately brief.

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, no-output-schema tool, the description covers the core mechanics: open profile, return text. However, it doesn't discuss prerequisites (logged in?), what the returned text looks like, or behavioral caveats around browser-driven scraping. Sibling-linked context (login/auth tools) implies a dependency but the description doesn't mention it.

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?

The tool has 0 parameters and 100% schema description coverage (which is trivially full for an empty schema). There's nothing for the description to add semantically since there are no parameters to explain. Baseline 4 for zero params is exceeded slightly because the description fully clarifies what data is returned.

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?

Describes opening the user's LinkedIn profile and returning visible profile text. Clear verb ('open') + resource (own profile) + outcome (return text). Differentiates from get_profile, which presumably gets another person's profile, though the description doesn't explicitly make this distinction.

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?

No explicit when-to-use or exclusion guidance. The 'My' in the name and 'your' in the description imply it's for the logged-in user's own profile, distinguishing it from get_profile, but this isn't stated as guidance. No mention of requiring login or alternatives.

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