get_context_for_query

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

No annotations provided. Description only states the basic function without disclosing any behavioral traits such as behavior on empty results, timeout, destructive potential, or output format. For a tool with no annotations, this is insufficient.

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?

Single sentence with no unnecessary content. Could be slightly more informative without losing conciseness, but currently efficient.

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 one parameter, no output schema, no annotations, and a sibling tool, the description is minimal. It lacks details on return format, error cases, or relationship to 'list_available_contexts'. Incomplete for practical use.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema's param description. Parameter is adequately documented by schema.

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 action ('Get') and resource ('relevant context prompt'), and implies query-based filtering. However, it does not explicitly distinguish from sibling 'list_available_contexts', though the query parameter suggests a targeted retrieval.

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?

Implies usage when a query is available and context is needed, but provides no explicit guidance on when not to use or how it differs from 'list_available_contexts'. No alternatives or prerequisites mentioned.

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