explore

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

No annotations are provided, so the description carries the full burden of disclosing side effects, authorization needs, or state changes. The description does not mention that some actions like 'rebuild_communities' or 'backfill_entities' likely mutate data, nor does it disclose read-only behavior, rate limits, or return characteristics. There is no behavioral transparency at all.

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?

The description is short and front-loaded with the main category, followed by an action list. There is no extraneous prose. However, the action list is not structured with descriptions or grouped by purpose, which limits its usefulness. Still, it earns its place as a compact enumeration.

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?

Given the tool's high complexity—24 parameters, 11 dispatching actions, and no annotations—the description is severely incomplete. It provides no per-action guidance, no parameter-action mapping, and no explanation of expected outputs or side effects. The presence of an output schema does not make up for the absence of operational context.

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?

The schema has 24 parameters with zero description coverage, and the description only lists possible values for the 'action' parameter without explaining their semantics. This is marginally helpful for understanding the required 'action' field, but it fails to clarify the purpose of the other 23 parameters, including relationships between them and the actions. The description does not compensate for the low schema coverage.

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 states the tool is for 'Graph & discovery operations' and lists eleven action names, which gives a broad sense of scope. However, it does not define any specific action or the resource it operates on, making it only slightly more helpful than the tool name. It is not a tautology, but it lacks the specificity needed to clearly distinguish individual operations.

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?

There is no guidance about when to use this tool versus its siblings, nor any context for choosing among the listed actions. The action list implies there are different modes, but no criteria or examples are provided. This leaves the agent without direction for selecting the correct operation.

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