gograph_dependents

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds that the server checks freshness and retries CHA/SSA after source changes, and explicitly states 'Read-only; no side effects.' 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?

Description is concise and well-structured: front-loaded with purpose, then technical details, usage guidance, and return info. Every sentence is informative with no redundancy.

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?

No output schema, but description explains return value: 'List of dependent package names and paths; empty when nothing imports the package.' Also covers freshness and retry behavior. Complete for understanding what to expect.

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 has 100% coverage with a description for the 'package' parameter. Description adds examples of valid formats (e.g., 'internal/auth', 'auth', or a full import path), providing additional 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?

Clearly states 'Find all packages that import the named package (inverse of gograph_deps).' The verb 'Find' and resource 'all packages that import the named package' are specific, and it distinguishes from sibling gograph_deps.

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?

Provides explicit 'WHEN TO USE' and 'NOT TO USE' sections, giving context for when to use this tool (before package-level interface change or removal) and when not (use gograph_callers for function callers, gograph_deps for outgoing imports). Excellent guidance.

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