get_page_content

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

No annotations are provided, so the description carries the full burden. It states it returns plain text with specific content types, but does not disclose any potential side effects, auth requirements, error handling, or constraints like formatting. For a read operation, it is adequate but lacks depth.

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 three sentences: purpose, content type, and usage guidance. It is front-loaded and every sentence adds value with no unnecessary words.

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 tool's simplicity (one parameter, output schema exists), the description covers purpose, return content, and usage. It lacks details on error cases or data freshness, but is fairly complete for a basic fetch tool.

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 input schema has one required parameter 'module_id' with 0% description coverage. The description mentions 'for a module' but does not explain what module_id is or how to obtain it. It adds minimal meaning beyond the schema, leaving the agent to infer from context.

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 'Fetch the text content of the course website page for a module' and specifies it returns 'lecture notes, explanations, and learning objectives as plain text.' It distinguishes from siblings like get_notebook_content and get_slide_content by referring specifically to the course website page for a module.

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 explicitly says 'Use this for conceptual questions about a topic,' providing clear context for when to use it. It does not mention when not to use it or explicitly name alternatives, but the sibling list is available.

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