test_retrieve_page_property

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

With no annotations provided, the description bears full responsibility for behavioral disclosure, yet it only states the basic operation. It fails to mention pagination behavior (start_cursor, page_size) or whether the tool supports filtering or has rate limits.

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 (one sentence), but it sacrifices necessary detail. For a tool with four parameters and a test variant, the brevity is insufficient, making it not optimally structured.

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 presence of pagination parameters, a test variant sibling, and an output schema (not detailed), the description is far from complete. It does not address output format, differences from the default version, or any limitations, leading to a significant knowledge gap for the agent.

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%, meaning the input schema provides no documentation for the parameters, and the tool description adds no information about what page_id, property_id, start_cursor, or page_size represent or how they should be used.

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 a specific page property' is a clear verb+resource, but it does not explain the purpose of the '[test]' prefix or differentiate this tool from the sibling default_retrieve_page_property. The agent lacks context on whether this is a sandboxed or experimental version.

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 the default variant or other test tools. The description gives no context about prerequisites, typical use cases, or scenarios to avoid.

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