wiki_page_resolve_id

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

The description declares read-only behavior, matching annotations. It adds context about being a lookup/preparation step, but does not detail error handling or response content beyond annotations, which already cover safety and idempotency.

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?

Two succinct sentences: one for purpose ('Read-only: get page_id...') and one for usage guidance, front-loaded with key read-only attribute. No superfluous words.

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?

Given the tool has an output schema and simple 2-parameter input, the description covers the core operation and usage context. It lacks mention of behavior when both parameters are provided or error cases, but these are minor for a straightforward lookup tool.

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 100% with parameter descriptions already explaining the format of url and slug. The tool description mentions these inputs in context but does not add new semantic detail beyond what the schema provides, warranting the baseline score.

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 resolves page_id from slug or URL, specifying it is read-only and a preparatory step for update/append. This distinctly sets it apart from sibling tools that get content or perform mutations.

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?

Explicitly advises using this tool before wiki_page_update or wiki_page_append_content when only slug or URL is known, providing clear when-to-use guidance and implicit exclusions for cases where page_id is already available.

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