get_context_status

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

Discloses return fields but no behavioral traits beyond that. No annotations provided, so description doesn't confirm read-only or safety. Minimal but not misleading.

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?

Single sentence, front-loaded with key information. Every word contributes; no fluff. Concise and clear.

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?

Covers essential output details despite lacking output schema. Could briefly clarify what 'latest session' refers to (e.g., current session vs last resumed), but overall sufficient for a simple parameterless tool.

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?

No parameters exist, schema coverage 100%. Baseline 4 applies because description doesn't need to add parameter details. No additional value needed but also no gaps.

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?

Clearly specifies verb 'Get', resource 'context window usage', and enumerates returned fields (used tokens, window size, percentage, model). Differentiates from siblings like get_quota_status and get_current_session by focusing on context usage.

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?

Implied usage for checking context usage, but no explicit guidance on when to use this versus sibling tools like get_quota_status or get_current_session. Adequate but lacks strategic direction.

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