get_context_stats

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

No annotations are provided, so the description carries full behavioral burden. It does not disclose whether the tool is read-only, whether it affects state, performance implications, or the return format. It only states the type of data returned.

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?

A single sentence with a clear front-loaded purpose. It is appropriately sized for a zero-parameter tool and does not waste words.

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 read-only tool with no output schema, the description is minimally adequate but lacks behavioral details like read-only nature, cache behavior, or how the statistics are computed. It gives the agent enough to know what the tool returns but not enough to confidently call it in all contexts.

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 has 0 parameters, so parameter semantics baseline is 4. No parameter information is needed or expected in the description.

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 states a specific verb and resource in Portuguese: 'Retorna estatísticas de uso de contexto (tokens estimados por categoria)'. It tells the agent it returns context usage statistics with estimated tokens per category, but does not differentiate from siblings like get_categories or get_prompt_summary.

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?

Implies usage for 'planejamento de context budget' but offers no explicit when-to-use, when-not-to-use, or comparison to alternatives. The sibling get_categories could also return category-related data, so the distinction is left to inference.

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