get_structure

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

With no annotations, the description carries full behavioral burden. It signals this is a read-oriented session-bootstrap call ('call this once') and describes the shape of returned data, but it never states read-only semantics, performance/caching implications, or what happens if called repeatedly.

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?

Two compact sentences with zero waste; the resource description comes first and the usage directive second, a natural front-loaded order.

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-argument query tool with an output schema that documents the return shape, the description supplies everything an agent needs: purpose, content, and session-timing. Nothing essential is missing.

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?

Zero parameters, so the baseline is 4; the description correctly implies no input filtering is needed and focuses entirely on return content.

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 the resource (category/project tree) and enumerates precisely what it contains: ids, open-task counts, labels by group, and strategies in use. It is clearly a structural-overview query, distinguishable from siblings like list_today or search_tasks, though it lacks an explicit verb and never contrasts itself with those siblings by name.

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?

Strong, specific timing guidance: 'Call this once at the start of a session,' plus the purpose of doing so ('it is how you map names to ids'). No alternatives or exclusions are named, which keeps it below 5.

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