session_links

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It only mentions the session_start prerequisite, which is a precondition rather than a behavior. It offers no information about read-only status, output format, error conditions, or side effects.

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 two short sentences with no redundant words or filler. It states the core purpose and a key prerequisite efficiently, achieving high conciseness and front-loading.

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?

Although an output schema exists (so return format is covered), the description is too sparse for a tool with one optional parameter and no annotations. It omits the meaning of max_links and fails to mention any error conditions, edge cases, or how it differs from similar tools. The prerequisite is noted, but the overall context is incomplete.

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 description does not mention the max_links parameter at all, and the schema provides only type and default with no explanatory text. With 0% schema description coverage, the description completely fails to explain the parameter's meaning or usage, leaving the agent to infer it from the parameter name.

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 (links) and context (current session page) but lacks an explicit verb such as 'get' or 'list', making it slightly less direct. It distinguishes from sibling tools like extract_links by specifying the session context, so the purpose is still unambiguous.

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 mentions 'Requires session_start', which implies it should be used after starting a session, but it does not explicitly contrast with alternatives like extract_links or state when not to use it. This provides some context but no direct usage guidance or exclusions.

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