list_entities

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It implies a read operation but does not state read-only safety, permissions, pagination behavior, or how include_archived changes the result set; the word 'every' may even mislead given the parameter's default false.

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 single front-loaded sentence with no filler, and it efficiently enumerates the key return fields. It is appropriately sized for the surface-level purpose it communicates.

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?

Because there are no annotations and the only parameter is undocumented, the description is not complete enough for confident invocation. The output schema covers return values, but usage context and include_archived semantics are missing, leaving significant gaps.

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 sole parameter, include_archived, has 0% schema description coverage and is never mentioned in the description. The description adds no meaning about what the flag controls or when it should be used, leaving the agent unable to invoke the tool with the parameter correctly understood.

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 clear verb and resource: 'List every wiki page,' and enumerates the returned fields (folder, name, version, last update, headline). It does not, however, differentiate this listing tool from siblings like load_wiki or clarify whether it is a complete dump versus a filtered view.

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?

There is no when-to-use guidance, no explicit alternatives, and no conditions for choosing list_entities over load_wiki or any other sibling. The agent is left to infer usage from the tool 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.