get_all_context

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly states the return format ('a dictionary mapping filename to file contents') and enumerates the files, which goes beyond the basic 'get' action. No side effects or limitations are mentioned, but none are expected for a read-only retrieval.

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, front-loaded with the main purpose, and then provides necessary detail about the return structure and file list. No fluff or redundant content.

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?

For a no-parameter, self-contained retrieval tool, the description is complete. It specifies the exact output format and scope, making it fully actionable for an agent without further elaboration.

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 tool has no parameters, so with 0 parameters the baseline is 4. The description correctly doesn't add parameter semantics since none exist, and the empty schema is fully sufficient.

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 'Get all personal context files at once' with a specific verb and resource. It lists the exact files included (identity, writing-style, opinions, expertise, projects, communication), which distinguishes it from the sibling get_writing_style.

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 phrase 'at once' implies this tool is for retrieving the full set of context files, but it does not explicitly contrast with the sibling tool get_writing_style or specify when not to use it. Usage context is implied rather than explicitly stated.

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