wikijs_get_page_by_id

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

No annotations provided; description only states it performs a read operation. Does not disclose side effects, authentication requirements, error behavior, or response format. Minimal transparency beyond basic purpose.

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?

Single sentence, front-loaded with verb and object. Every word earns its place. No unnecessary elaboration.

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 single-parameter retrieval tool, the description covers the key information. However, lacking output schema means agents miss what the response contains; slight gap in completeness. Still sufficient for basic usage.

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 already describes the 'id' parameter as 'Wiki page ID.' Description adds 'numeric' but this is redundant since schema type is 'number'. Schema coverage is 100%, so baseline 3 is appropriate; description adds no significant extra meaning.

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?

Description clearly states 'Get a single page body/content by numeric page ID.' It identifies the specific verb, resource, and method of identification, distinguishing it from sibling tool wikijs_get_page_by_path which uses a path.

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 explicit guidance on when to use this tool versus alternatives like wikijs_get_page_by_path. The context of numeric ID is implied but not contrasted with other retrieval methods. Adequate but lacks explicit usage context.

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