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. It states the output type (metadata) but says nothing about required inputs, error behavior, rate limits, or response format. The minimal description leaves the agent uncertain about prerequisites and edge cases.

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 (a single phrase), which is concise but not appropriately sized. It lacks any structural elements like parameter explanations or usage context. The brevity here is under-specification rather than efficient communication.

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?

Despite having an output schema (not shown), the description provides no information about return values or expected input. For a tool with one undocumented parameter and no behavioral hints, the description is far from complete. An agent cannot confidently invoke this tool based on the provided text.

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 schema has one parameter 'q' with a default of empty string, but schema description coverage is 0%. The description does not explain what 'q' represents (presumably a page title or query). The agent has no information on how to fill this parameter correctly, making the tool effectively unusable without external knowledge.

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 clearly identifies the resource (Wikipedia page) and the specific attributes (page length, last edit, editor). It distinguishes itself from siblings like 'wikipedia' (page content) and 'wikisummary' (summary) by focusing on metadata. However, it lacks an explicit verb like 'Retrieve' or 'Get', making it a noun phrase rather than a clear action statement.

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 on when to use this tool versus alternatives. It does not mention that it should be used for metadata retrieval or when page content is not needed. The agent must infer usage from the name and description alone.

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