Backfeed Metadata

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful constraint context that source_sync is the only graph commit/checkpoint/reconcile authority and backfeed is unsupported, but it does not explain side effects, auth requirements, or what 'serving' actually mutates.

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 opening sentence is front-loaded, but the paragraph mixes metadata_snapshot return details, source_sync authority rules, an unsupported backfeed warning, and a concept tag. It is short but not cleanly structured; several clauses read as internal vocabulary rather than actionable tool guidance.

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?

An output schema exists, so return values need not be explained. However, the description still leaves the tool's operation, params_json contents, and relationship to metadata_snapshot/source_sync ambiguous, which is a significant gap for even a one-parameter tool.

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 single params_json parameter is already documented in the schema. The description adds no format, expected keys, or constraints for params_json, making baseline 3 appropriate.

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 first line names a verb and resource, but 'certified metadata-only source projection' is opaque and the same paragraph says 'Backfeed is explicitly unsupported,' undermining what the tool is actually for. It references metadata_snapshot and source_sync but never clearly states this tool's role relative to them.

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?

No explicit trigger or condition for when to call this tool is provided. Instead it names other components (metadata_snapshot, Agent Connector SDK source_sync) and says backfeed is unsupported, leaving the positive use case and prerequisites unclear.

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