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

Annotations correctly declare a non-readOnly, non-idempotent, non-destructive write with no contradiction. The description adds valuable behavioral rules beyond that: never include secrets/API keys/tokens, and tell the user the feedback was sent. It does not cover auth/prerequisite behavior or rate limits.

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?

Front-loaded with purpose and triggers, and every sentence earns its place (secret caution, user notification). It is a dense run-on block that lists parameters inline rather than as a clean structure, which slightly hurts scanability.

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 simple feedback-submission tool with no output schema, the description covers triggers, parameter meaning, and safety constraints well. It omits what the call returns (confirmation/id) and any auth expectations for the API key, which is a minor remaining gap.

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 33% (botId, projectApiKey), but the description compensates by explaining category (with full enum values), message, context (with example content), and agentName in prose. It does not clarify botId or projectApiKey beyond the schema, but overall adds substantial semantic value.

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 feedback to the TestChimp team) and frames it as the agent-facing 'contact us' channel. The trigger list makes it clearly distinct from sibling reporting tools like create-issue, report-*-findings and report-agent-action.

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?

Enumerates five explicit when-to-use triggers: TestChimp bug/confusing error, user struggle or complaint, missing capability, and wrong/unclear skill or docs. It is clear about context but names no alternatives or when-not-to-use conditions (e.g. use create-issue instead for a logged defect).

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