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

With no annotations, the description carries the full burden and does disclose meaningful traits: authenticated via project API key with project resolved from the key, and the hard constraint that Activity/timeline attachment requires both workflowId and a stable workflowExecutionId (don't mint a new ULID per issue). It still omits idempotency, error behavior, and what a create returns.

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 core purpose is front-loaded in the first sentence, followed by progressively more specific guidance, and for a 27-param tool with zero schema coverage the length is largely justified. It is dense single-paragraph prose with some run-on content that could be better structured, but few sentences are pure 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?

Given a high-complexity create tool with nested objects, no annotations, and no output schema, the description supplies enough to call it correctly for the main scenarios (common create, TASK_ISSUE, traceability). Remaining gaps are the undocumented secondary traceability params and lack of any return-value or failure expectations.

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 0% across 27 params, so the description must compensate and largely does: it enumerates the curated contract fields and adds real semantics for labels ("TestChimp Implement"), severity mapping from task priority, category, linkTargets ordinals, and agentTraceability. It leaves several traceability fields (gitSha, actorType, branchName, cliVersion, policyVersion) without meaning, so it is strong but not complete.

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+resource ("Create a TestChimp issue in the current project") and names the primary scenario. It also distinguishes itself from siblings by explicitly preferring this over report-agent-action for issue creates, so an agent can route correctly without opening another schema.

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 context: simple fields for common creates vs. --json-input for the full contract, plus the specific /testchimp TASK_ISSUE recipe. It names an alternative (report-agent-action) and when to prefer this tool, but never states an explicit when-not-to-use or failure condition.

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