get_schooling_detail

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

The description indicates the tool fetches details and mentions an optional html_only parameter, which adds some transparency. However, without annotations, it does not disclose authentication dependencies, error behavior, or security constraints beyond 'secure portal'.

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, well-structured sentence that efficiently conveys the tool's purpose and key parameter usage. No extraneous information.

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 retrieval tool with two parameters and no output schema, the description adequately covers the main functionality. It could be improved by noting the return structure or common error conditions, but the current level is sufficient for basic selection.

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 description adds meaning beyond the schema by explaining that entry_id identifies the application and that html_only returns raw HTML instead of parsed data. This enriches the schema's basic parameter descriptions.

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 action (Fetch), the resource (schooling application details), and the unique identifier (entry ID). It implicitly distinguishes from sibling tools like get_schooling (which likely lists applications).

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 use when needing details for a specific entry, but does not explicitly contrast with list retrieval or mention when not to use it. No alternative tool is named, though the presence of get_schooling suggests context.

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