get_paragraph_text_from_document

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get text' implies a read-only operation, it doesn't specify whether this requires document access permissions, how paragraph indexing works (0-based vs 1-based), what happens with invalid indices, or if there are rate limits. The description provides basic intent but lacks important operational details.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the core functionality immediately.

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 tool with 2 parameters (0% schema coverage), no annotations, and no output schema, the description is inadequate. It doesn't explain parameter requirements, behavioral constraints, error conditions, or return format. Given the complexity of document processing and the lack of structured documentation elsewhere, the description should provide more operational context.

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 for both parameters, the description provides no information about what 'filename' should contain (path, name, format) or how 'paragraph_index' is interpreted. The description mentions 'specific paragraph' but doesn't clarify indexing semantics or valid ranges, leaving parameters essentially undocumented.

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 action ('Get text') and target resource ('from a specific paragraph in a Word document'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_document_text' or 'find_text_in_document', which offer different text extraction approaches.

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 provides no guidance on when to use this tool versus alternatives like 'get_document_text' (for full document text) or 'find_text_in_document' (for text search). There's no mention of prerequisites, limitations, or appropriate contexts for paragraph-based extraction versus other text retrieval methods.

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