get_context

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

With no annotations, the description carries the behavioral burden. It discloses the return type ('dict') and lists top-level keys (projects, areas, tags). However, it inconsistently lists 'headings' in the first sentence but omits them from the return dict, leaving ambiguity about whether headings are a separate key or nested. It also never explicitly states the operation is read-only, though the verb implies it.

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 three short sentences, front-loading the core function and then adding the return shape. Every sentence earns its place with no filler or 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?

For a no-arg getter with no annotations and no output schema, the description gives the essential purpose and a high-level return structure. However, the incomplete return disclosure (missing 'headings') and the lack of detail about areas and tags leave an agent with less than full information about what it will receive. The startup context is helpful for judging when to call it.

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 zero parameters with 100% coverage, so the baseline is 4. The description implies a no-argument call ('in one call') but does not explicitly say no parameters are needed. No further parameter detail is required.

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 ('Get') and resource ('all structural metadata'), then enumerates projects, areas, tags, and headings. This clearly differentiates it from sibling tools like get_dashboard, get_review_data, and get_project_health, which target other data categories.

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 second sentence states that this replaces 3-4 separate MCP calls needed at startup, giving a clear when-to-use signal. It does not explicitly name alternate tools or exclusion conditions, but the startup/consolidation context is strong and not misleading.

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