hyperspace_pdk_extension

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether extension actions are read-only or destructive, what permissions are required, how errors are surfaced, or that behavior varies by extension/action pairing.

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 definition is a single front-loaded sentence with no filler. The parenthetical list is dense but still concise and every part contributes an example or capability hint.

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?

For a gateway tool that dispatches to arbitrarily many extensions, with a nested payload object, no annotations, and no output schema, the description is incomplete. It lacks guidance on discovering valid extension/action pairs, payload schemas, permissions, side effects, and expected results.

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 the baseline is 3, but the description adds useful meaning by associating extension names with capabilities, such as git_ast for AST indexing/blast radius and embed for Markdown ingestion. It still does not explain how action values must pair with extensions or what payload shape each action expects.

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, 'Invoke', and a concrete resource, 'native HyperspaceDB PDK Extension', with examples such as 'git_ast' and 'embed'. It is distinguishable from core database siblings, though it never explicitly says it is the routing path for extension actions rather than those core 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?

The example extensions and brief capability notes imply when the tool is useful, but there is no explicit when-to-use versus when-not-to-use guidance. It does not tell the agent how this relates to sibling tools like hyperspace_search_text or hyperspace_explore_graph.

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