get_page

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

The description adds the deprecated status, which is useful behavioral context. However, with no annotations, it does not disclose what the tool actually does (e.g., side effects, safety, return format). The behavior is only implied via the alias, so the agent must inspect get_debug_page to fully understand.

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 a single sentence, front-loaded with the most important fact (deprecated) and the alternative. No wasted words.

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 what is essentially a deprecated alias with no parameters and no output schema, the description is completely sufficient. It tells the agent everything needed: don't use this, use get_debug_page instead.

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 tool has zero parameters, so the description does not need to provide parameter details. The schema confirms this with an empty properties object. The baseline of 4 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 clearly identifies the tool as a deprecated alias of get_debug_page, which tells the agent its purpose by referencing the canonical tool. It does not directly state what the tool does, but the alias relationship makes the purpose evident.

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 explicitly says 'Deprecated alias' and names the alternative tool (get_debug_page). This is a clear directive to avoid this tool and use get_debug_page instead, providing both when-to-use (never) and an alternative.

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