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

Annotations only declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds the materially important behavior: the first call does NOT send anything, it only previews and returns confirm_token, and the user must consent before the real submission. That is exactly the kind of interaction-protocol detail annotations cannot convey.

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?

Three densely packed sentences: purpose first, constraints second, the critical two-step protocol last. Every clause carries operational weight (send-as-user, length bounds, preview semantics, consent gate) with no filler.

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?

With no output schema, the description still explains what the first call returns (confirm_token) and what the second call requires, which is the only return information an agent needs. Combined with the length bounds and enum intent mapping, nothing required to call this correctly is missing.

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 only 33% (only confirm_token is described in the schema), so the description must compensate, and it does: it maps the free-text intent onto the kind enum (bug / feature idea / other) and supplies the 10–5000 character bounds for message. It adds clear value, though it does not explicitly name the enum literals 'enhancement' or 'other'.

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 and resource ('Send a bug report, feature idea or other feedback to the Instadram team') and uniquely identifies the tool among siblings — nothing else in the list submits feedback. It also names the in-product analogue (Profile → Send Feedback), which pins down what the tool actually does.

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?

Gives clear operating context: send feedback 'as you', 10–5000 characters, and the two-step preview-then-confirm protocol with the precise condition for the second call ('only after they agree'). No competing alternative exists among siblings, so the absence of an explicit 'use X instead' clause is not a real gap.

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