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

With no annotations provided, the description carries the full behavioral disclosure burden. It does well by stating that the call 'Returns 202', is asynchronous, involves a human fetching and checking the artifact, and triggers a pipeline re-run. It also directs the agent to check_status for tracking, which sets accurate expectations for a non-immediate, human-in-the-loop process.

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 three sentences that each convey meaningful information: the core purpose, the response behavior, and the tracking mechanism. The 'INFLUENCE' prefix is unexplained but not padded, so the overall structure remains efficient.

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?

The description covers the submission lifecycle well enough for basic invocation: it tells the agent what happens after submission and how to track it. However, given five parameters, no annotations, and no output schema, significant gaps remain around the meaning of slug and contact, possible error conditions, and how the submitted artifact is identified in later checks. It is minimally viable but not fully complete.

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 description coverage is only 40%, and the description adds no parameter-level meaning for slug, url, or contact. It only vaguely refers to 'an artifact you publish', which does not clarify what slug represents, how url is used, or what contact is for. The schema has useful notes for type and context, but the description fails to compensate for the undocumented fields.

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 clearly states the tool's function: 'tell us about an artifact you publish, rather than waiting for us to find it.' It names a specific action and resource, and contrasts it with passive discovery. It could be slightly clearer by naming the relevant sibling alternatives (e.g., find_artifacts) but the intent is not ambiguous.

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 phrase 'rather than waiting for us to find it' gives an implicit when-to-use signal, and 'Track it with check_status' points to the follow-up tool. It does not explicitly name alternatives or exclusions, but the submission-vs-discovery contrast is sufficient for an agent to select this tool in the intended situations.

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