get_document_info

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

No annotations exist, so the description carries full burden for behavioral disclosure. It fails to mention return format, side effects (none likely), prerequisites (e.g., active document must exist), or any constraints. The verb 'Get' implies a read operation, but no details are given.

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 a single sentence, which is concise but underspecified. It lacks necessary details to be useful. While it is front-loaded, it does not earn its place due to vagueness.

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 no parameters, no output schema, and no annotations, the description is insufficient for an agent to understand what the tool returns or how it differs from siblings. The tool's scope is ambiguous.

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?

With zero parameters, the input schema fully covers all parameters (none). The description adds no parameter info, but baseline for 0 parameters is 4, as the schema is inherently complete.

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 'Get information about the active document' – a generic verb-resource pair. However, it fails to specify what kind of information, making it vague and indistinguishable from numerous sibling tools like get_document_colors, get_document_elements, etc. Neither specificity nor differentiation is provided.

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 on when to use this tool versus alternatives. There are many get_document_* sibling tools with more specific purposes, but the description offers no criteria for choosing this generic tool.

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