Report a problem

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

Annotations show non-read-only and non-destructive. Description adds context: do not include personal data, and message should describe the issue. It does not mention rate limits or auth, but the behavioral constraints are clear.

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?

Description is efficient with a bullet list of conditions. Every sentence adds value, though the list could be integrated more smoothly. Overall, it is well-structured and not verbose.

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?

Given the tool's simplicity (4 params, 1 required, no output schema), the description covers usage context, parameter guidance, and privacy constraints. It is fully sufficient for an agent to decide and invoke the tool correctly.

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 describes all 4 parameters with 100% coverage. Description adds value by instructing what to put in 'message' (what was being done and what went wrong), and reminds to keep it short and avoid sensitive data. This goes beyond the schema's brief summaries.

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?

Clearly states the tool reports problems with Apify's MCP tools or Actors. The verb 'Report' and resource 'problem' are specific, and it is distinct from siblings that handle actors, datasets, or docs.

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?

Explicitly lists when to call (tool missing, errors, timeout, confusing results, can't complete request) and what to avoid (personal data, secrets, verbatim conversation). No alternative tools are mentioned, but the conditions are clear and actionable.

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