Ingest Topology Contribution

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety/mutation profile is covered. The description adds the "validated" precondition, which is genuine extra context, but says nothing about duplicate handling, overwrite behavior, or storage location.

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?

A single efficient sentence with no filler, and the mutation verb is front-loaded. It is terse to the point of under-specification rather than padded.

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?

A mutation tool with no output schema, one undocumented string parameter, and no explanation of what a valid payload looks like or what ingestion produces. Too little is said for an agent to call this correctly without inspecting sibling tools.

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?

One required parameter (payload) at 0% schema description coverage, and the description gives no hint of its format, structure, or expected content. With coverage this low the description should compensate for the gap and does not.

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 ("Store") and resource ("contribution") scoped to a workspace, so an agent knows it is a write operation. However, it never names or distinguishes itself from validate_topology_contribution or the other topology_* siblings, relying on the reader to infer the pipeline position.

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 only usage signal is the word "validated," which faintly implies running validate_topology_contribution first. There is no explicit when-to-use, no statement of the precondition for the payload, and no mention of alternatives.

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