list_site_pages

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says the tool lists pages and shares filters with another tool, without mentioning pagination behavior, state semantics, language handling, or any other runtime behavior.

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 or duplication. It front-loads the core purpose and uses the sibling reference efficiently.

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 five-parameter list operation with no annotations, this description is underspecified. It does not explain what 'site pages' are, what filter values are accepted, or how this tool relates to list_landing_pages beyond filter similarity. The output schema reduces the need to describe return values, but the input behavior remains unclear.

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 0%, so the description must explain the five parameters, but it does not. The reference to list_landing_pages may indirectly help an agent that already understands that sibling, but it does not define limit, state, language, name_contains, or updated_after.

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 states a clear action and resource ('List site pages'), which is enough to know what the tool does. The cross-reference to list_landing_pages hints at scope but does not clarify how site pages differ from landing pages.

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?

There is no guidance on when to use this tool versus alternatives like list_landing_pages or get_page. The only usage note is 'Same filters as list_landing_pages,' which describes parameter similarity, not selection conditions.

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