gograph_callees

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

Annotations already indicate read-only, no side effects, idempotent. Description adds that it requires .gograph/graph.json, is read-only with no side effects, and describes return format. 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?

Highly concise with bullet points; every sentence adds necessary information. Purpose is front-loaded.

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?

Despite lack of output schema, description fully explains return value (list of callees with details) and edge case (empty when no calls). Also covers prerequisites.

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 covers 100% parameter description. Description adds value by specifying that 'function' supports short names, dot-notation, or fully-qualified IDs, going beyond 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 clearly states the tool finds callees of a function (one-hop fan-out), using specific verb 'find' and resource 'callees'. It distinguishes from siblings by mentioning upstream callers and transitive dependencies.

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 provides 'WHEN TO USE' and 'NOT TO USE' sections, naming alternatives gograph_callers and gograph_deps. Also includes prerequisite (run gograph build first).

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