get_daily_setups

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

Annotations already indicate safe read-only behavior. The description adds the critical behavioral fact that the tool is deprecated, which is beyond what annotations provide. No contradictions.

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?

A single sentence is maximally concise for a deprecation notice. It front-loads the essential 'DEPRECATED' warning and immediately gives the replacement.

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?

While the deprecation notice is helpful, the description lacks any information about the tool's original purpose, parameter semantics, or output format. An agent cannot effectively use this tool even if it wanted to.

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 provides zero explanation of the parameters (top, timeframe) or how they affect results. The agent has no guidance on using them.

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 does not explain what 'daily setups' are or what the tool originally did; it only states deprecation. The agent must infer purpose from the name and sibling tools, but no explicit purpose is given.

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?

Explicitly advises against using this tool and provides a direct alternative: 'use discover(mode="daily_setups", ...)'. This is clear and actionable.

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