anchor_fetch

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

Annotations already cover readOnly, idempotent, and openWorld hints. The description adds the deprecation context, which is important behavioral information beyond structured fields. No other behavioral traits disclosed, but the bar is lowered due to annotations.

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?

Single sentence, front-loaded with deprecation warning and alternative. Zero waste; every word earns its place in the context of a deprecated tool.

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 the tool is deprecated and an alternative is fully specified, the description is complete for its primary purpose of redirecting usage. However, it does not explain return values or original behavior, which may be needed if the tool is still invoked. Output schema exists but is not referenced.

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%, requiring the description to explain parameter semantics. The description only mentions parameter names in the alternative call example without any explanation of their meaning, format, or constraints. Completely fails to add value beyond the schema.

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 tool is deprecated and directs to an alternative, but does not explicitly state what the tool does. The verb 'fetch' is implied but not clarified. It is vague and relies on the alternative to infer purpose.

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 says the tool is deprecated and to use 'context' instead. Provides clear when-not-to-use guidance and specific alternative syntax, which is excellent for guiding agent behavior.

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