read_specific_document

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

No annotations provided, so the description carries full burden. It claims to read full file content but the schema includes a page parameter for pagination, creating ambiguity. It does not disclose error handling, file format, or size limits, leaving critical behavioral gaps.

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 front-loads the purpose. It could be more structured to include usage guidance or pagination clarification, but it efficiently conveys the core action.

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 no output schema and two parameters, the description lacks completeness: it does not explain return values, pagination behavior, file type, or how to discover available files. The context signals show a 100% parameter coverage, but the description fails to integrate that into a coherent operational guide.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter context beyond what the schema already provides (fileName must match exactly, page for paginated content).

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 reads full documentation file content when complete context is needed. It uses specific verb 'Read' and resource 'documentation file content', distinguishing it from siblings like search_documentation (searching) and get_document_index (listing documents).

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 usage when complete context is needed but does not explicitly state when to avoid this tool or mention alternatives. It lacks guidance on prerequisites like file existence or how to find the exact fileName, though schema provides a must-match requirement.

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