Create Tracker queue macro

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), lowering the burden. The description adds the semantics of what is being created and notes it 'Returns the new macro', but discloses no permission requirements, idempotency behavior, or failure modes beyond the annotation hints.

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?

Two short sentences, front-loaded with the core purpose followed by parameter notes and the return statement. No filler; the sizing is appropriate for a two-parameter create tool.

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 nested-body create tool with no output schema, the description covers the essence and notes the return value, and annotations cover the safety profile. However the naming mismatch (``fieldChanges`` vs ``issue_update``) and the unmentioned required ``queue_id`` leave gaps an agent must resolve from the schema.

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 100%, so the baseline is 3. The description does mention ``name`` as required and characterizes ``body`` as the comment template, but it never mentions the required ``queue_id`` and refers to ``fieldChanges`` rows, a name that does not appear in the schema (which uses ``issue_update``), so it adds limited and slightly inconsistent value over the schema.

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 ('Create a macro on a queue') and even defines what a macro is ('a canned comment plus field updates applied on demand'), which is more than the title alone. It does not explicitly name the sibling operations (tracker_macros_update/delete) to distinguish itself, but the create-vs-read/update/delete distinction is inferable from the name.

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?

No explicit when-to-use, when-not-to-use, or alternative tool is named. Usage is only implied by the definition of a macro and the fact that this is a create operation among read/update/delete siblings. Adequate but leaves routing to inference.

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