get_homepage_blocks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a simple return statement by revealing that content is frequently an embedded image rather than text, that images is usually where the information lives, and that include_html returns raw inner HTML. It also clearly describes the return structure and provides an example.

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 well-structured with a front-loaded purpose, a brief context paragraph, and clearly labeled Args/Returns/Examples sections. Every sentence adds value – no filler or repetition of the schema.

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 one optional parameter and no annotations, the description covers purpose, usage context, return format, parameter semantics, and an example. It is complete enough for an agent to select and invoke the tool correctly without additional information.

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 schema only describes include_html as a boolean with default false. The description adds substantial meaning: it states that the flag makes the tool 'also return each block's raw inner HTML' and shows usage in the example. With 0% schema description coverage, the description fully compensates.

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 uses a specific verb ('Retrieve') and resource ('the 'in de kijker' blocks pinned to the Smartschool homepage'). It also distinguishes this tool from siblings by explaining the unique nature of these blocks: recurring content that is never sent as a message and never lands in a document 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 provides clear context for when to use the tool (recurring homepage content like monthly menus, calendars, announcements) and explicitly states what these blocks are not (messages or document module content), effectively excluding get_messages and get_attachments. However, it does not name alternative sibling tools directly.

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