get_properties

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

Annotations are absent, so the description must disclose all behavioral traits. It only indicates a read operation and lists return fields, but omits information about permissions, error behavior for missing documents, or any side effects. The return type is partially covered by an output schema, but the description adds minimal behavioral context.

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 concise sentence that conveys the core function. However, it is not front-loaded with the most critical information (e.g., parameter explanation) and could benefit from a slightly structured format.

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?

Despite an existing output schema, the description lacks context about when to choose this tool over siblings like get_document_info (which may return more comprehensive info) or set_properties. The parameter remains unexplained, and no usage context is given, leaving the agent underinformed.

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 single parameter 'document_handle' is not explained in the description. With 0% schema description coverage, the agent receives no context about what this parameter represents (e.g., document ID, filename, or path), making correct invocation difficult.

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 retrieves core document properties and lists specific examples (title, creator, subject, dates, revision), making the purpose immediately obvious and distinguishing it from property-related siblings like get_custom_properties or set_properties.

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 such as get_document_info or get_custom_properties. The description does not mention prerequisites, limitations, or when not to use it.

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