context.gather

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

Annotations declare readOnlyHint=true, so the description adds value by describing the output (scored snippets, ranked) and method (knowledge graph). However, it does not disclose any potential limitations, rate limits, or authentication needs. The description is consistent with annotations, no contradiction.

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 that efficiently communicates the core purpose and output. It is front-loaded and contains no redundant information.

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 3 parameters (one required), multiple siblings, and a potentially complex output (scored notes with snippets), the description lacks sufficient detail. It does not clarify what 'related context' means, how scoring works, or how parameters influence results. The presence of an output schema reduces the burden but does not compensate for missing parameter explanations and usage context.

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 0% description coverage, and the description provides no explanation of the three parameters (path, maxNotes, maxTotalBytes). The agent must infer meaning from names alone, which is insufficient for correct invocation.

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 the tool gathers related context for a note via the knowledge graph and returns scored snippets ranked by strength. The verb 'gather' and resource 'related context' are specific, and the output format helps distinguish it from siblings like context.retrieve or graph.get_neighbors, though not explicitly.

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 guidance on when to use this tool versus alternatives. The description does not mention scenarios where context.gather is preferred over context.retrieve or graph.get_neighbors, nor does it state when not to use it.

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