mediumrelated

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, 'mediumRelated' gives no information about what the tool does, whether it's read-only or mutative, what it returns, or any operational constraints like rate limits or authentication needs.

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?

While the description is extremely concise with just one word, this represents under-specification rather than effective brevity. It lacks any structure or front-loading of critical information, making it unhelpful despite its short length.

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 has no parameters and no output schema, the description should fully explain what the tool does and returns. 'mediumRelated' provides none of this, leaving the agent completely in the dark about functionality, behavior, or output format in a context with many similar-sounding sibling tools.

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 0 parameters with 100% schema description coverage, so there are no parameters to document. The baseline for zero parameters is 4, as the description doesn't need to compensate for any parameter documentation gaps, though it fails to provide other necessary information.

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?

Tautological: description restates name/title.

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 offers no guidance on when to use this tool, when not to use it, or what alternatives might exist among the many sibling tools. There is no mention of context, prerequisites, or comparison with similar tools like 'related' or 'recommend'.

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