gograph_capabilities

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

Adds significant value beyond annotations: states it's 100% local, read-only, no side effects, no auth, no rate limits, no destructive modifications. Annotations already declare readOnlyHint=true, but description adds context like 'static analysis tool' and return format.

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?

Well-structured with sections for purpose, behavior, usage, and completeness. Front-loaded with main purpose, no redundant sentences, concise yet informative.

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 no output schema, description explains return as 'structured checklist of all 50 tools, workflows, limitations'. Complete for a discovery tool with no parameters.

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 exist, and schema coverage is 100% vacuously. Description explains no parameters needed, which is adequate. Baseline for 0 params is 4.

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 it discovers gograph MCP tools, their purposes, workflows, and limitations. It distinguishes itself from sibling tools by being the overview tool, mentioning 'all 50 available tools'.

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 advises to call this tool first and not repeatedly once cached. Provides clear when-to-use guidance and implies alternatives (specific tools after this).

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