rca_graph_get

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

Description adds format details and return type, but annotations already cover safety (readOnlyHint, idempotentHint). No additional behavioral context like authentication or rate limits.

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?

Short, front-loaded, single sentence plus bullet list. No redundant information, though some parameter info could be integrated more tightly.

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?

Covers core purpose and return value, but lacks explanation of token and client_id parameters. With low complexity, it's adequate but not thorough.

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?

Description explains graph_id and format (with enum values), but omits token and client_id. Schema description coverage is low, so description partially compensates.

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 verb 'retrieve', resource 'causal graph', and supported formats (JSON, DOT, adjacency). Distinguishes well from sibling tools like create/delete.

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?

Does not explicitly state when to use or when not to use this tool versus alternatives, nor prerequisites like needing a valid graph_id.

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