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

With no annotations, the description carries the full behavioral burden. The '[PUBLIC READ/WRITE]' tag is ambiguous for a retrieval tool and never explained, and the description does not say how large the graph response can be, whether depth is bounded, or what the returned structure looks like; only the token-cost hint adds any real behavioral context.

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?

Two tight sentences with the resource identified first and the token-cost guidance second; nothing is wasted. The bracketed access tag is the only slightly noisy element.

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 exists, so the description should ideally sketch the return shape for a graph query, which it does only loosely. Given a simple 3-parameter, zero-required schema, it is close to sufficient but leaves the response format and the READ/WRITE semantics unexplained.

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 coverage is 100%, so all three parameters are already documented, including the token-saving purpose of summary_only. The description restates that advice but adds no syntax, defaults, or interaction details (e.g., how max_depth combines with focus_node_id) 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?

States a specific verb (Retrieve) and two named resources (knowledge synapse graph, DyTopo active communication graph), which distinguishes it from item-level siblings like get_knowledge_item or search_knowledge. The '[PUBLIC READ/WRITE]' prefix muddies rather than clarifies what the resource is.

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?

Gives concrete guidance on which parameters to use to limit token cost ('Use summary_only or focus_node_id to minimize token usage'), but says nothing about when to choose this tool over graph-adjacent siblings such as search_knowledge, read_map_links, or get_knowledge_item. Usage is only implied.

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