gograph_orphans

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

Description adds value beyond annotations: requires .gograph/graph.json and a prior build command, declares no side effects, and describes the return format. No contradiction with annotations (readOnlyHint=true, destructiveHint=false).

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?

Efficiently includes purpose, prerequisites, usage guidance, and return details in a few sentences. Slightly verbose with structured sections, but still concise overall.

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?

With no parameters and no output schema, the description fully covers the tool's purpose, prerequisites, behavior, and return value. Provides complete context for invocation.

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?

No parameters in input schema; baseline score is 4 as per guidelines. Description adds no parameter-specific info, but none is needed.

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?

Specific verb+resource combination: 'Find all functions and methods unreachable from any entry point' clearly states the action and scope. Distinguishes from sibling tools by mentioning alternatives like gograph_usages and gograph_callers.

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 states when to use (during code cleanup, dead-code audits) and when not to use (for specific usages), with named alternatives. Provides clear context for decision-making.

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