get_paragraph

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

The description states it retrieves text and style, but with no annotations provided, it fails to disclose any behavioral traits like read-only nature, permission requirements, or limitations.

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 plus argument format) and front-loaded with the primary purpose, though the Args section could be integrated more elegantly.

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?

For a simple retrieval tool with an output schema, the description is adequate but incomplete due to lack of parameter coverage for document_handle and absence of usage context. Baseline score reflects minimal viability.

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 description explains the para_id parameter with a format example but omits the optional document_handle parameter, which has no schema description (0% coverage). This leaves parameter meaning incomplete.

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 specifies the verb 'Get' and the resource 'paragraph' with a clear identifier 'paraId', distinguishing it from sibling tools like get_paragraph_format.

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_paragraph_format or get_runs. The description lacks context for tool selection.

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