context_get_architecture

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

With no annotations provided, the description carries the full burden. 'Inspect' reasonably implies a read-only operation and the listed element types clarify scope, but the description does not disclose return format, potential side effects, or failure behavior. It adds some behavioral context but not rich detail.

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. The parenthetical list is useful and specific without bloating the text. It earns its place.

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 zero-parameter inspection tool, the description covers the essential purpose and scope. However, with no output schema and no annotation, the agent is left without information about the return value, and the lack of differentiation from architecture_analyze/architecture_plan leaves selection somewhat uncertain.

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 takes zero parameters and schema coverage is 100%, so the baseline is 4. The description still adds value by clarifying what the tool actually inspects, making the no-parameter invocation sensible.

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 names a specific verb ('Inspect'), a specific resource ('communication and dependency architecture'), and enumerates concrete elements (RemoteEvents, RemoteFunctions, BindableEvents, shared ModuleScripts). However, it does not explicitly distinguish itself from sibling architecture tools such as architecture_analyze or architecture_plan, so the differentiation is only implied.

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 gives context about what is being inspected but provides no explicit guidance on when to use this tool versus alternatives like architecture_analyze or project_dependencies. There are no stated exclusions, prerequisites, or conditions indicating the appropriate use case.

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