get_page_linked_references

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

No annotations exist, so description carries full burden. It only states 'fetch' without disclosing read-only nature, response format, or whether any state changes occur. Minimal behavioral context.

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 extremely concise, but this is under-specification rather than efficient communication. A single sentence with no wasted words, yet lacks necessary details.

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?

Given low complexity, one required parameter, and no output schema, the description still fails to provide enough context for an agent. Sibling tools are diverse, and this description does not help distinguish usage.

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 single parameter 'page_name' is described only by its type and name in the schema. The description adds no extra meaning, such as expected format (e.g., title vs ID, full path constraints). With 0% schema description coverage, description fails to compensate.

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 states the tool fetches linked references for a page, which is a specific verb+resource. It distinguishes from siblings like 'get_page' and 'get_page_blocks_tree' by focusing on linked references.

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 guidance provided on when to use this tool vs alternatives (e.g., 'get_page' or 'search'). No context on prerequisites or scenarios where this is appropriate.

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