list_homepages

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, indicating a safe, idempotent read operation. The description adds that it lists 'homepage dashboards (CMS content pages used as homepages)', which clarifies scope but doesn't add behavioral traits beyond annotations. No contradiction noted.

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 concise sentence that front-loads the action and resource. Every word is necessary, and there is no superfluous information. It efficiently communicates the tool's 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?

The description is minimal and does not mention return format or typical fields, which could be helpful given no output schema. However, for a simple list tool with clear annotations, it is adequate but leaves room for more context, such as differentiating from other list tools or specifying what is returned.

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%, with both parameters (query, limit) already described. The description does not add any additional meaning or context for the parameters beyond what is in the schema, so 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 clearly states 'List homepage dashboards (CMS content pages used as homepages)', providing a specific verb and resource. It distinguishes from siblings like list_pa_dashboards and list_portal_pages by specifying that these are homepages, i.e., CMS content pages used specifically as homepages.

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 guidance is given on when to use this tool versus alternatives. Among sibling tools, there are many list_* tools, but the description does not provide any when/when-not or exclusions. This leaves the agent without differentiation cues.

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