rush_pr_synthesize

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and artifact; it does not say whether the tool reads the repo, creates a PR, modifies an existing PR, requires authentication, or what the 'synthesis' actually does. The description is not misleading, but it provides almost no behavioral transparency.

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 description is a single concise sentence with no filler or repetition. It is appropriately short for a one-parameter tool, though the wording is somewhat stilted and under-specified. Brevity itself is not the issue; content depth is.

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?

Even though an output schema exists, the description leaves fundamental questions unanswered: what exactly a 'pull request card' is, what source data is used, and how base_branch affects the output. For a tool with dozens of siblings, this description is not sufficient for an agent to confidently invoke it.

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%, and the description never mentions base_branch. The schema's title 'Base Branch' and default 'main' are self-explaining, but the description adds zero context about how the base branch affects the synthesized PR card. Because coverage is low, the description needed to compensate but did not.

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?

Description uses verb 'Synthesize' plus object 'structured semantic pull request card,' so it does name a deliverable. However, 'card' and 'semantic' are undefined, and nothing distinguishes this from sibling tools like rush_review or rush_commit_msg. It is slightly more than a restatement of the name, but still vague.

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?

There is no guidance about when to use this tool, when not to use it, or which sibling alternative might be better. With approximately 60 sibling tools, selection is left entirely to inference from the name. The description provides no context for choosing this over rush_review, rush_commit_msg, or similar tools.

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