search_erp_pages

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

The description discloses that it returns page paths, but lacks details on partial matching, case sensitivity, pagination, or other nuances. With no annotations, the description provides basic but minimal behavioral context.

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 brief (two sentences plus examples) with no redundancy. Every part contributes value: stating the action, result type, and illustrative examples.

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, has output schema), the description covers the essential purpose and result. It could mention the output schema or add behavioral details, but is largely adequate for an agent.

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 0% coverage for parameter descriptions. The description adds the keyword 'search' and concrete examples ('grades', 'fee', etc.), compensating for the schema's lack of parameter detail and clarifying the query parameter's meaning.

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 tool searches for ERP pages by keyword and returns matching page paths. It uses a specific verb ('search') and resource ('ERP pages'), and the sibling tool 'browse_erp_page' suggests a complementary action, distinguishing this tool's purpose.

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 versus alternatives like 'browse_erp_page' or other search tools. The examples imply usage for finding pages by keyword, but no exclusions or context are provided.

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