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

With no annotations, the description discloses session persistence and return values. However, it omits potential side effects (e.g., rate limits, authentication requirements, or destructive actions), leaving the agent partially informed.

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?

Three sentences plus a code example, all essential. Information is front-loaded with purpose, return values, and session behavior. No fluff.

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?

Covers return values and session persistence, which is sufficient for a navigation tool without an output schema. Could mention HTTP method and body usage, but not critical.

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 coverage is 100% with descriptions for all 4 parameters. The description adds a call format example (identity_id and url) but does not elaborate on 'body' or 'method' beyond what the schema provides, adding minimal new insight.

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?

Clearly states the action 'Navigate to a URL' using a specific resource 'Presence identity's persistent session'. Distinguishes from sibling tools like presence_act or presence_extract by focusing on navigation and session persistence. Also lists returned data (page title, text, links, HTTP status, cookies).

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?

Implicitly suggests use for navigating with a persistent session and mentions cookie carry-over, but does not explicitly state when not to use this tool or provide alternatives among the presence siblings.

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