related

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The single word 'related' reveals nothing about whether this is a read/write operation, what resources it affects, authentication requirements, rate limits, or expected behavior. This leaves the agent completely in the dark about how the tool behaves.

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 technically concise with just one word, this represents under-specification rather than effective brevity. The description fails to convey necessary information about the tool's function. True conciseness balances brevity with completeness, which this description does not achieve.

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 complexity implied by having 70+ sibling tools and no output schema, the description is completely inadequate. A single word cannot provide sufficient context for an agent to understand when and how to use this tool effectively. The description fails to compensate for the lack of annotations and output schema.

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 with 100% schema description coverage, so there are no parameters to document. The description doesn't need to compensate for any parameter documentation gaps. While the description doesn't add parameter semantics (since there are none), this is appropriate for a parameterless tool.

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 versus alternatives. With 70+ sibling tools including various list, detail, search, and discovery tools, there is no context about appropriate use cases, prerequisites, or exclusions. The single-word description fails to provide any usage direction.

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