list_homepages

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

Annotations already declare readOnlyHint and openWorldHint, covering safety and openness. The description adds the definition of 'homepage dashboards' as CMS content pages used as homepages, which is useful context, but does not discuss pagination, query behavior, or the implications of openWorldHint. It neither contradicts annotations nor adds substantial behavioral detail.

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, front-loaded sentence that states the action and clarifies the resource without any redundant words. It earns its place and wastes no space.

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 read-only listing tool with two optional parameters, the description plus schema is fairly complete. It defines the concept of 'homepage dashboards' which adds contextual meaning, though it could optionally mention return format or relation to other page types. Minor gap, but adequate.

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 coverage is 100% with descriptions for both 'limit' and 'query'. The tool description does not add any parameter information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 'List homepage dashboards (CMS content pages used as homepages)' clearly states the action and resource, and the parenthetical differentiates it from broader page-listing tools like list_portal_pages. The verb 'List' is specific and the scope is well-defined.

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 a user needs homepage dashboards but provides no explicit context, alternatives, or exclusions. There is no mention of when to prefer this over list_portal_pages or other listing tools, leaving usage fully implied.

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