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

No annotations are provided, so the description carries the full disclosure burden. It hints that the deliverable is a "copy-paste prompt pack with examples," which is the one useful behavioral clue, but it says nothing about whether the tool is a read-only generator, what side effects exist, or what the response looks like. Marketing adjectives substitute for behavioral facts.

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?

It is short, but the two sentences are almost entirely promotional filler ("production-ready", "repeatable workflow you can run today") and none of it is front-loaded function. Every sentence could be replaced by a single concrete statement of what the tool audits and returns.

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?

The tool is simple (one optional parameter, no annotations, no output schema), yet the description never states what the audit produces or how it relates to the dense perf-* family around it. The "prompt pack" phrase is the only concrete information and it is not elaborated. Not adequate for selection in this sibling set.

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?

The single `query` parameter is fully documented in the schema (100% coverage) as "Optional user query to scope the analysis," so the schema does the work. The description adds no meaning about how the query affects output or what form it should take. With complete schema coverage, the baseline 3 applies.

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?

"perf audit tool system" restates the tool name and title rather than defining the operation; the rest is marketing copy ("production-ready", "you can run today"). It never says what is being audited (marketing performance? employee performance? site performance?) or what the caller gets back beyond the vague phrase "copy-paste prompt pack". It does not distinguish this tool from the nine perf-* siblings.

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 when-to-use guidance at all, and no mention of the obvious alternatives (perf-check-tool, perf-gen-tool, perf-tpl-tool, perf-summary-tool). "For marketing and operations leaders" names an audience, not a triggering condition or a prerequisite. An agent has no basis for choosing this over a sibling.

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