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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description contributes real behavioral facts: the link is single-use and expires in 15 minutes. That is exactly the kind of context annotations cannot express. It omits the security weight of the link (it grants full dashboard access) and that a credential is required, which keeps it from a 5.

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 sentence with zero filler; the defining properties (one-time, 15-minute) are placed immediately after the artifact so an agent scanning the first clause already knows the key constraint.

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 two-optional-parameter tool with no output schema, the description should state that the result is the link itself (a URL string) and where it can be used. It says 'in the browser' but never confirms the return value, leaving the agent to infer what comes back from a call with readOnlyHint=false.

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%, so both 'page' and 'api_key' are already documented with examples and fallback behavior. The description mentions 'dashboard' and 'browser', loosely gesturing at the page parameter, but adds no syntax, defaults, or constraints beyond the schema. Baseline 3 applies.

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 names a specific artifact ('a one-time link') and its effect ('signs the owner into their infobro dashboard in the browser'), which is unambiguous and clearly distinct from every sibling (whoami, verify_signup, etc.). It stops short of a 5 only because it is phrased as a noun phrase rather than stating the action ('generate/create a sign-in link').

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 is implied by the purpose — an agent can infer this is for handing the owner a browser session — but there is no explicit when-to-use, no statement of prerequisites (owner identity, valid API key), and no mention of alternatives such as whoami for identity checks. Nothing misleading, just unstated.

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