push_to_tracker

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

With no annotations, the description carries the full load and does well: it discloses the safe-by-default dryRun preview, the idempotency-ish skip of already-sent items, and the mutating effect of update: true. It stops short of stating required permissions, failure behavior, or whether already-linked items can be duplicated.

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?

Four short sentences, front-loaded with the core behavior, then edge semantics (skip, update, dryRun), then the prerequisite. No filler and nothing important 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 4-parameter mutation tool with no annotations and no output schema, the description covers what gets created, what is skipped, how to preview, how to refresh, and the prerequisite. The remaining gap (return value shape) is implied by 'lists what would be sent' and is minor.

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 50% (dryRun and projectId are undocumented in the schema), and the description compensates by explaining dryRun's default and effect ('only lists what would be sent') and update's meaning. limit and projectId remain explained only by name/schema; the description adds no syntax or scoping detail for projectId.

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 (create) plus the exact resource mapping: one Task per requirement, one Story per user story. That is far more precise than the name alone. It does not, however, differentiate itself from the sibling sync_tracker, which an agent may see as overlapping.

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 concrete operating guidance: items already sent are skipped, update: true refreshes linked items, dryRun only previews, and the tracker must be set via set_project_tracker first. Missing only an explicit statement of when to prefer sync_tracker or re-run behavior after configuration changes.

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