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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Coreference: Coreference' reveals nothing about side effects, mutability, return behavior, or operational constraints. There is no behavioral information at all.

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 extremely short, but this is under-specification rather than conciseness. There is no useful content to structure or front-load. Every word is wasted on tautology.

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?

There is no output schema, no annotations, and the description explains nothing about the operation or its parameters. For a tool with four parameters and a highly ambiguous name, this is completely inadequate for an agent to select and invoke it correctly.

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% with descriptors like 'Input to process' and 'Label to process', but these are generic and uninformative. The description adds no meaning beyond the schema; it does not clarify what 'input', 'label', 'labels', or 'content' mean in the context of coreference. With four ambiguous parameters and no helpful description, a low score is warranted.

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 is 'Coreference: Coreference', which is a tautology that merely restates the tool name. It provides no verb, no resource, no operation, and no distinction from the hundreds of sibling tools. An agent cannot determine what this tool actually does.

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 guidance is given about when to use this tool versus any alternative. The description is purely a repetition of the tool name with no context, no scenario, and no exclusions. The agent is left with zero information about selection.

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