get_document_statistics

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

The description states it returns statistics or an error, but provides no details on side effects, permissions, or potential pitfalls. With no annotations, the description should disclose safety guarantees (e.g., read-only), but it does not, leaving behavioral assumptions to the agent.

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 concise—two sentences with clear front-loading of the main purpose. Every phrase earns its place; no unnecessary words 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?

Given the existence of an output schema (though not visible here), the description suffices for basic understanding. However, it lacks guidance on how this tool relates to similar siblings (e.g., get_document_info, get_word_count), which would help the agent choose correctly.

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, so no parameter documentation is needed. The description adds value by listing example statistics included, clarifying what 'comprehensive' means beyond the empty schema.

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 it retrieves comprehensive document statistics like paragraph, word, and table counts, effectively conveying the tool's purpose. It distinguishes from generic get_document_info, but does not explicitly differentiate from specific counter tools like get_word_count or count_paragraphs.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_word_count, get_tables_info, count_paragraphs). The agent must infer usage from the description alone, which lacks contextual alternatives or when-not-to-use advice.

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