List Page Properties

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds minimal behavioral context (key filtering, pagination) but does not explain return format, errors, or permission needs. No contradiction with annotations.

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 concise and well-structured with a one-sentence summary and a clearly formatted Args list. It is efficient, though the 'Page ID' explanation adds little value over the schema title, and the overall content is sparse.

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 tool is simple, has strong annotations, and no output schema. The description covers the essential purpose and parameters but lacks contextual guidance like when to use it versus get_page_property or what the return structure represents. Adequate for a basic list tool but with clear gaps.

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 0%, so the description's arg explanations ('Filter by property key', 'Pagination cursor', 'Max results') add basic meaning beyond the schema's bare titles. However, these explanations are minimal and do not elaborate on formats or defaults beyond what is already inferable from the schema.

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 content properties on a page' uses the specific verb 'List' and clearly identifies the resource ('content properties') and scope ('on a page'), distinguishing it from sibling tools like get_page_property (singular) and create/update/delete property tools.

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 provides no explicit guidance on when to use this tool versus alternatives such as get_page_property, nor does it mention pagination behavior or scenarios where the key filter would be appropriate. It merely states the action without context.

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