cortex_get_state

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

No annotations provided, so description carries full burden. It discloses that the state is compressed (<200 tokens) and that it includes a token budget warning if >50% used. Though it doesn't declare read-only, the verb 'Get' implies no modification, and the behavioral detail is adequate for a simple getter.

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 sentences, no wasted words. The first sentence front-loads the primary action and usage advice, and the second adds a key behavioral detail. Highly concise.

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 low complexity (one param, no output schema), the description covers the tool's purpose, size constraint, usage timing, and a behavioral warning. It doesn't detail the return format or state fields, but for a lightweight state getter this is sufficient.

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?

Only one parameter ('session_id') with schema description 'Session ID for token budget check'. The tool description reiterates this purpose, adding no new semantic value. With 100% schema coverage, baseline score of 3 is appropriate.

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 gets a compressed project state under 200 tokens, and advises to call before every action. It distinguishes itself from siblings like cortex_get_detail and cortex_get_token_budget by emphasizing the compressed nature and the token budget warning.

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?

Explicitly instructs to call before every action, providing clear context for when to use. Does not mention when not to use or alternatives, but the directive is strong and useful.

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