get_context

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

No annotations are provided, so the description must cover behavioral traits. It lists returned fields but does not mention any side effects, permissions, rate limits, or whether it is read-only. The term 'generated summary/context' implies a fetch, but explicit read-only hint is missing.

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 two sentences with zero waste. It front-loads the purpose ('A node's generated summary/context') and immediately explains parameter usage. Every word earns its place.

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's simplicity (2 params, no output schema), the description covers the basics. However, it does not define 'node' or its relationship to sibling tools, and it lacks output details (e.g., format of the returned fields). Additional context would help.

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 0%, so the description compensates well: it explains that 'id' is for a single node and 'ids' for multiple nodes. This adds meaning beyond the bare schema. Could be improved by specifying format or constraints.

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 returns a node's generated summary/context with specific fields (title, summary, etc.). It distinguishes between single and batch retrieval via 'id' vs 'ids'. However, it does not differentiate from sibling tools like 'get_source' or 'get_minimal_context'.

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 basic guidance on using 'id' for one node and 'ids' for multiple nodes, but lacks when-not-to-use instructions or alternatives among siblings. No explicit context for selection.

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