set_project_tracker

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

With no annotations, the description carries the full burden. It usefully discloses the one-shot/immutable-after-send semantics, but says nothing about credential or authorization requirements for Jira/GitHub, what error occurs when the binding is rejected, or whether any remote state is created.

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 short sentences, each doing distinct work: capability, timing requirement with examples, and the immutability constraint. The binding verb leads, so nothing important is buried.

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 3-param mutation with no annotations and no output schema, the description covers purpose, timing and the hard constraint well. Remaining gaps (auth prerequisites, return/confirmation behavior) are minor but real given the zero annotation coverage.

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 `target` is documented), so the description must compensate — and it does: it names the enum values for `kind` and restates the accepted formats ('Jira project key, e.g. PROJ', 'owner/repo'). Only `projectId` is left implicit by context.

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?

Specific verb+resource: 'Bind a project to its work tracker' with the two supported kinds (jira/github) enumerated in parentheses. An agent can tell this configures tracker integration, but the description doesn't explicitly distinguish it from sibling tools like push_to_tracker or sync_tracker.

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?

'Set it once, before sending anything' gives a clear timing condition, and 'A project with items already sent cannot change tracker' gives an explicit exclusion. It stops short of naming the related sibling operations (push_to_tracker, sync_tracker) that depend on this setup.

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