get_context

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

The description states it 'Get's data but offers no details on behavioral traits like side effects, authorization needs, rate limits, or error conditions. Without annotations, the agent has minimal insight into the tool's behavior beyond the action.

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 with no extraneous words. It is front-loaded with the verb and immediately lists the key outputs, making it efficient and easy to parse.

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 description explains what the tool retrieves but lacks details on the output format or structure. Given the absence of an output schema, the agent would benefit from knowing whether the data is returned as a list, object, or plain text. This gap moderately limits completeness.

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?

The input schema has no parameters, so the description bears full responsibility for explaining the tool's functionality. The description effectively conveys that the tool retrieves user context, including interests, tech stack, and affinities, which adds value beyond the empty 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?

The description uses a specific verb 'Get' and clearly lists the resources: user's interests, tech stack, and learned affinities. It is distinguishable from sibling tools like 'agent_memory' which focus on storing memories rather than retrieving user 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage independently.

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