get_ai_context

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

With no annotations, the description bears full responsibility for behavioral transparency. It mentions using `--accept-security-risk` to bypass interactive prompts, which is good. However, it does not disclose whether the generated file persists, if any resources are modified, or potential side effects like overwriting. Safety and mutation traits are not fully addressed.

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 concise (about 5 sentences) and well-structured with a clear overview followed by parameter and return details. Every sentence adds value, though the example could be integrated more tightly. No redundancy.

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 no annotations and an output schema exists (implied), the description explains what the output contains and its purpose. However, it omits details like naming conventions, potential errors beyond a generic error message, and behavior upon repeated calls. It is functional but not exhaustive for a read-like operation.

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 coverage is 0%, so the description must compensate for the single parameter `master`. It provides format guidance ('Master filename inside the working directory') and an example value. This adds meaningful context beyond the schema's bare name. No further details on validation or constraints are needed.

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 the tool generates and returns the full AI Context file for a master. It specifies what the file contains (network state and CLI command reference) and that it invokes an internal command. While it distinguishes from siblings like get_network_state and export_master_xlsx by focusing on AI Context, it could be more explicit about uniqueness.

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 use when an AI Context file is needed for planning multi-step edits, but it lacks explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, though sibling tools exist for other export functions. The guidance is adequate but not thorough.

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