refresh_catalog

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

No annotations are present, so the description must disclose all behavioral traits. It mentions 'Admin-only' and 'Refresh', but does not explain effects on existing data, whether the operation is destructive, or the behavior of the 'force' parameter. The schema description partially covers the parameter's behavior, but the tool description lacks sufficient transparency.

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 extremely concise—two short sentences with no filler. It front-loads the critical admin constraint and clearly states the action. Every word serves a purpose.

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 no output schema and one parameter, the description is incomplete. It lacks details on return values, side effects, or when the refresh actually writes. Despite simplicity, more context is needed for full clarity.

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 100%, so the schema already documents the single 'force' parameter. The tool description adds no additional parameter info, meeting the baseline for this dimension.

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 verb 'Refresh', the resource 'endpoint catalog', and the source 'JustSerpAPI OpenAPI documents'. It also notes 'Admin-only' as a constraint. This distinguishes it from sibling tools like call_endpoint or search_endpoints, which serve different purposes.

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 usage when you need to refresh the catalog and are an admin, but it does not explicitly state when to use versus alternatives. No guidance on prerequisites or when not to use is provided.

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