getPageProperties

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only the action ('Get'), with no information about permissions required, rate limits, side effects, response format, or error conditions. For a read operation with no structured safety hints, this is a significant gap in 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 at three words, with no wasted verbiage. However, this conciseness comes at the cost of under-specification, but as per scoring rules, it's efficient in structure.

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?

Given the complexity of a page properties retrieval tool with no annotations, no output schema, and a parameter with 0% schema coverage, the description is completely inadequate. It fails to explain what properties are returned, how to interpret them, or any contextual nuances, making it insufficient for effective tool use.

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?

The input schema has 1 parameter with 0% description coverage, and the tool description provides no information about the 'pagePath' parameter. It doesn't explain what format the path should be in, examples, or constraints, leaving the parameter entirely undocumented beyond its name and type.

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 'Get page properties' is a tautology that essentially restates the tool name, providing no additional specificity about what 'properties' entails or what resource is being accessed. It distinguishes from siblings like 'getPageContent' or 'getPageImages' only by the generic term 'properties', but doesn't clarify what types of properties (metadata, configuration, status, etc.) are retrieved.

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 provided on when to use this tool versus alternatives. With siblings like 'getPageContent', 'getPageImages', 'getAllTextContent', and 'getPageTextContent', the description offers no indication of what distinguishes 'properties' from 'content' or other page-related data, leaving the agent with no basis for selection.

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