docx.sdt_get

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

With no annotations available, the description carries the sole responsibility for behavioral disclosure. It only states 'Get SDT content' without addressing side effects, return format, or whether it's read-only. The lack of any behavioral traits or error handling information leaves significant ambiguity for a tool that likely performs a read operation.

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 extremely concise, consisting of a single four-word phrase. It is front-loaded and contains no fluff, earning a perfect score for conciseness. Every word serves a purpose, and it is appropriately sized for a simple getter operation.

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 lack of annotations, output schema, and parameters, the description must compensate but does not. It fails to explain what 'SDT content' means, what format the return value takes, or any conditions that affect the output. For a tool with this minimal metadata, the description is inadequate for an agent to fully understand its behavior.

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 accepts zero parameters, and the schema coverage is 100%, so there are no parameters to describe. Following the baseline for zero parameters, the description does not need to add parameter-related information. The absence of parameters is clear from the schema, and no additional semantics are required.

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 'Get SDT content' provides a clear verb and object, which distinguishes it from sibling tools like docx.get_text or docx.sdt_put. However, it largely restates the tool name 'sdt_get' and adds minimal specificity beyond implying handling of structured document tags. The description is functional but lacks detail that would help a novice understand what SDT stands for or its role in the document.

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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, the type of content expected, or any comparison with similar tools like docx.get_text or docx.find. Since no usage context is provided, the agent receives no help in selecting this tool appropriately.

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