About Commertize

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context by stating the content is static reference text rather than live data, and by summarizing the covered topics, though it does not discuss return format or permissions (the output schema handles returns).

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?

A single front-loaded sentence carries the purpose, the when-to-use instruction, the enumeration of content areas, and the static-vs-live distinction without any wasted clauses. Every part earns its place.

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 parameterless documentation tool with annotations covering safety and an output schema covering returns, the description supplies everything an agent needs: what it is, what it contains, and when to read it. No gaps remain.

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?

With zero parameters, there is no parameter semantics to convey, so the baseline of 4 applies. The description correctly does not attempt to invent parameter details.

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?

The description states a specific resource (curated reference text about Commertize) and enumerates exactly what topics it covers, distinguishing it from the sibling tools that list, get, or search live data. An agent can immediately tell this is background/context material rather than an operational tool.

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?

It explicitly says an agent 'should read before using the other tools' and contrasts this with 'Static text, not live data', giving clear when-to-use and when-not guidance. The alternative is implicitly all live-data siblings, which is sufficient for a documentation tool.

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