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

With no annotations, the description carries the burden of behavioral disclosure. It openly states that the tool is not live and returns a structured 'feature_not_available' response, which is valuable behavioral context beyond the tool name.

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 concise and front-loads the essential 'not live yet' caveat. It wastes no words, though it could be slightly more helpful with a one-line alternative or usage note.

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?

The description adequately communicates the stub-like state and expected unavailable response, especially with an output schema present. It is incomplete, however, in guiding the agent toward an alternative or clarifying whether accepting limit/cursor has any effect.

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 description coverage is 0%, and the description does not explain limit or cursor beyond the resource context of listing links. The parameter names and schema hints provide some meaning, but the description fails to compensate for the lack of schema descriptions.

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 states the resource and action ('List links') clearly, and the 'not live yet' caveat clarifies the current state. It does not explicitly differentiate from sibling tools like get_link, though plural 'links' implies a list operation.

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 the tool should not be used for actual listing because the REST list is not live yet. However, it does not provide explicit when-to-use guidance or point to an alternative sibling for list operations.

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