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

Annotations already cover read-only/destructive hints; the description adds beyond that by disclosing the external backend ('Powered by api.meshtool.ai') and the cost ('4 MESH/call'), plus the 'any JSON shape' output flexibility. It does not detail failure or truncation behavior, but the schema notes length limits.

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 core purpose is front-loaded in one clear sentence, and the cost/backend metadata is compact. The trailing parenthetical '(4 MESH/call, a tool · extraction)' is somewhat noisy, but the overall definition is short and scannable.

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 simple extraction tool with no output schema, the description plus annotated schema covers what to pass, the expected shape capability, and cost. It does not explicitly spell out the response object, but 'Pull structured data out' and the user-provided shape make it adequately inferable.

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 mostly restates text/shape and does not add much meaning beyond the schema. It reinforces shape flexibility via 'any JSON shape you describe' but adds no new parameter-level semantics.

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 leads with a specific verb and resource: 'Pull structured data out of free text' and enumerates concrete use cases (classification, field extraction, scoring). The title and category tag 'extraction' also help distinguish it from generic text tools in the sibling list.

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 gives clear context for when to use it: whenever you want a JSON-shaped result extracted from free text, and even lists example jobs. It does not explicitly exclude alternatives or state when not to use it, so it stops just short of a 5.

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