get_deep_link_algo_urls

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

No annotations are provided, so the description carries full burden. It only states the action and returns, omitting behavioral traits like side effects, auth requirements, or error conditions beyond a generic raise clause.

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 short and includes structured Args/Returns/Raises sections. The deprecation note is front-loaded. It is efficient but could be more explicit about the return type.

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 deprecated tool, completeness is less critical, but the description lacks explanation of what 'algo URLs' are and does not fully leverage the output schema. Parameters are only partially documented.

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%, but the description documents 'site_url' as 'The URL of the site'. However, 'self' is not described, leaving one parameter undocumented.

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 retrieves 'algo URLs with deep links', using a specific verb and resource. It distinguishes from siblings like 'get_deep_link' by adding 'algo', though 'algo' is not defined.

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 explicit '(Deprecated)' provides usage guidance to avoid new use, but no alternative tool is suggested. Siblings exist (e.g., 'get_deep_link'), but no replacement is mentioned.

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