get_page_content

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

No annotations are present, so the description must disclose behavioral traits. It only says 'get', implying a read operation, but does not state safety (read-only), authentication requirements, potential large payloads, pagination, or error behavior. There is no mention of what the response contains beyond 'full body' or whether it's HTML, plain text, etc. The description is too minimal to be transparent.

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 with no fluff. It front-loads the core action and resource, and the selector is mentioned succinctly. Every word earns its place, and it is appropriately short for a simple getter.

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?

The tool has an output schema (which may document return values), but the description does not mention it or any error conditions, authentication, or prerequisites. The need for a course_identifier is completely absent from the description, and the notion of a 'URL slug' might be ambiguous (full URL vs path segment). Given the large sibling set, the description does not help the agent choose correctly or prepare the call, so it is incomplete for effective use.

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 clarifies that 'page_url' is the URL slug, adding some meaning, but gives no explanation of 'course_identifier' (its role, format, or how to obtain it). The description fails to specify that a course context is required and offers no guidance on constructing a valid request. This leaves significant ambiguity for the agent.

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 states a clear action (get), a specific resource (full body of a wiki page), and the identifying mechanism (URL slug). This distinguishes it from list_pages, which lists page metadata, and from get_syllabus/get_front_page, which target fixed pages. An agent can tell exactly what this tool does and when it is relevant.

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. There is no mention of when to prefer it over list_pages (e.g., when full content is needed) or any exclusions, requirements, or context such as needing to first call list_pages to obtain the slug. The description merely states functionality without usage conditions.

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