node_get

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

Annotations already indicate read-only, non-destructive, and idempotent. The description adds that the tool returns 'full pages array — one entry per language', which is useful context beyond annotations. No contradictions, but no mention of rate limits or other constraints.

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 sentences, front-loaded with the main purpose. The second sentence adds specific usage guidance. No wasted words, though the structure could be slightly improved by separating parameter explanations.

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 no output schema, the description partially explains the return value (full pages array per language) but not the exact structure. For a simple get operation with two required params, it's adequate for usage but leaves parameter details unexplained.

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 has two required parameters (site, node_id) with 0% description coverage. The description only mentions 'node id' in usage context but does not explain 'site' or the format/constraints of node_id. With no parameter descriptions, the agent may guess incorrectly.

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 'Get a single node by id' with the specific verb 'Get' and resource 'node'. It distinguishes from siblings like 'nodes_list' by mentioning 'full pages array — one entry per language' and provides a specific use case for parallel translation.

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 says 'Use this when preparing a parallel translation' and outlines a workflow: 'read the node id from one page, then pass node_id to page_create with the second-language details'. This provides clear when-to-use and an alternative tool (page_create).

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