get_paragraph_format

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

The description accurately lists the returned formatting attributes, providing insight into the tool's behavior. Since it is a read operation and no annotations are provided, the description adequately discloses the scope.

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 succinct, with a clear opening sentence and a bullet-like Args block. Every sentence adds value, and there is no extraneous text.

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?

The description covers the main purpose and returned attributes, which is sufficient for a simple read tool with an output schema. It could mention error cases like missing paragraph, but overall it is complete.

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 0% schema description coverage, the description fully explains the only parameter 'para_id' as 'paraId of the target paragraph', compensating for the lack of schema documentation.

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 'Read all formatting attributes of a paragraph' and lists specific attributes (style, alignment, indentation, etc.), distinguishing it from siblings like 'get_paragraph' that retrieve content.

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 implies a read-only operation but does not provide explicit guidance on when to use this tool vs alternatives, nor does it mention how to obtain the para_id.

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