Get Context

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the tool either fetches a single key or lists all context, but it does not clarify return format, whether the project parameter is required, or what happens when both parameters are omitted. The verb 'get' implies read-only, but the description adds little beyond the schema.

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, front-loaded sentence with no filler. Every phrase contributes to understanding the core behavior and the primary branching condition.

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?

The tool has optional parameters and no output schema, yet the description does not explain whether 'project' is needed for key retrieval, what happens if both fields are omitted, or what the returned context structure looks like. This leaves ambiguity for an agent deciding how to invoke the tool correctly.

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 the schema already documents both 'key' and 'project'. The description adds the high-level relationship between key and listing all context, but does not provide additional parameter meaning beyond what the schema already offers.

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 states a clear verb ('Get') and resource ('context'), and expresses the two modes: retrieve by key or list all for a project. It is distinct enough from siblings like set_context, though it does not explicitly contrast itself with query or search.

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 implies when to use the tool (when you need context by key or all context for a project) but gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as query, search, or get_project_summary.

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