get_page

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

With no annotations, the description adds some behavioral insight by stating it returns a Page object with title, body (HTML), and metadata. However, it omits safety traits like read-only nature, authentication requirements, or error handling. The description provides moderate value but not fully comprehensive.

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 with exactly two sentences of purpose and clearly structured Args and Returns sections. Every sentence adds value with no fluff.

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 tool with 2 parameters and no output schema, the description is adequate but incomplete. It lacks details on behavioral context (e.g., auth, errors) and usage guidance. However, it covers the core functionality and return format.

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 0%, so the description must compensate. It names both parameters and provides an example for page_slug, adding meaning beyond the schema. It could offer more detail on constraints (e.g., page_slug format pattern) but the provided info is helpful.

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 'Get a single page by its URL slug.' This provides a specific verb and resource, and is distinct from sibling tools which focus on assignments, courses, etc.

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 explicit guidance on when to use this tool vs. alternatives. While the purpose implies it's for fetching a single page when you have a course ID and slug, there is no mention of exclusions or conditions. The context is implied but not elaborated.

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