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

With no annotations provided, the description must carry the full behavioral disclosure burden. It only says 'Page extract/description for a topic' without explaining what the extract contains, limitations (e.g., missing pages, disambiguation), or permission requirements. This is minimal for an unannotated tool.

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 a compact single phrase, front-loading the purpose with no filler. It is appropriately concise for a simple one-parameter tool.

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?

Although the tool is simple and has an output schema, the description lacks sufficient context given the large group of siblings. It does not clarify what kind of summary is returned or when to use this instead of similar tools, leaving an agent to guess.

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 coverage is 0% for the single parameter 'q'. The description implies the parameter is a topic by saying 'for a topic', but it does not explicitly map q to the topic, state whether it is required, or provide format expectations. It adds only bare meaning over the schema.

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 states the tool provides a Wikipedia page extract/description for a topic, making the resource and action explicit. However, it does not differentiate from sibling 'wikipedia' or 'wikidata', which may also provide article content.

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 prefer this tool over closely related siblings like 'wikipedia', 'wikidata', or 'nearbywiki'. There is no mention of alternatives, prerequisites, or exclusion conditions.

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