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

With no annotations provided, the description carries the full burden, and it does so thoroughly: it discloses verification status for API-key vs anonymous reports, update semantics for repeated application_id calls, author visibility of specific fields, and identity privacy. These are exactly the behavioral traits an agent needs beyond the schema.

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 front-loaded with purpose and trigger conditions, then moves to persistence, update behavior, and privacy constraints. Every sentence adds operational value, and the format is easy to scan despite covering several distinct behavioral aspects.

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 tool with conditional parameter requirements and an output schema, the description plus schema fully cover what an agent needs: when to call, what outcomes exist, update semantics, author visibility, and privacy rules. The output schema handles return values, so no additional explanation is required.

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% and the schema already provides detailed per-field descriptions and conditional requirements. The description adds useful privacy/visibility context for certain fields, but does not add much parameter-level meaning beyond what the schema already contains, so the baseline of 3 is 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 description opens with a specific verb and resource: 'Report what happened when you applied an asset you fetched with get_asset_content.' It names the four outcome categories, making the tool's function unmistakable and clearly distinct from the retrieval-focused siblings.

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?

It explicitly states when to call ('once you know: applied as is, applied with changes, broke, or not applicable') and provides useful downstream context about search results. It does not explicitly say when not to use it or name alternatives, but the trigger condition is clear enough for correct selection.

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