redmine_wiki_page_get

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals only the HTTP method GET, which implies a read operation, but says nothing about return format, error behavior, or the effect of the include parameter. This is insufficient for a tool with no annotation coverage.

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 sentence with no wasted words, and the action and endpoint are front-loaded. However, it's so terse that it forfeits useful context. It earns a high score for efficiency, but a perfect score would require a better balance of brevity and informativeness.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't explain the include parameter, the return value shape, or error handling, leaving an agent to guess important invocation details. The endpoint provides some context, but not enough to call the tool with confidence.

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 only 33% (just 'project id or identifier' for project_id), and the description adds no explicit parameter details. The endpoint hints that project_id and title are path parameters, but the include parameter is entirely unexplained. The description does not compensate for low schema coverage.

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 explicitly states the action 'Get' and the resource 'wiki page', and the endpoint pattern clarifies the exact operation. This clearly distinguishes it from siblings like redmine_wiki_pages_list and redmine_wiki_page_create_or_update, which are obviously different actions.

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?

The description gives no guidance on when to use this tool versus alternatives. It doesn't contrast with redmine_wiki_pages_list or redmine_wiki_page_create_or_update, and an agent would have to infer from the endpoint alone that this is for retrieving a single page by title.

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