Get Plone Content

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

No annotations are provided, so the description carries the burden of disclosure. It correctly implies a read-only operation ('Retrieves') and uses 'full JSON data' to convey the response format. However, it does not mention error behavior (e.g., missing path) or permission requirements, but for a simple retrieval, the information is sufficient.

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?

Two sentences plus an example are extremely concise and front-loaded with the primary purpose. Every word is necessary. No fluff.

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?

No output schema exists, so the description should offer more detail about the return structure. 'Full JSON data' is vague; agents may need to infer fields. Given the context signals (no output schema, no nested objects), the description is adequate but not complete.

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 100%, so the description's param info is additive but not critical. The description provides an example call and clarifies that path can be '/' for root, which adds minor value beyond the schema's 'e.g.' examples. Meets baseline for high schema coverage.

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?

Description clearly states the verb 'Retrieves', the resource 'full JSON data for a single content item', and the mechanism 'using its path'. An example call is provided, making the purpose unmistakable. It effectively distinguishes from sibling tools like plone_search which handles multiple items.

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 implies the tool is for retrieving a single content item by path, but it does not explicitly specify when to use it versus alternatives like plone_search or plone_get_site_info. Lacks guidance on exclusions or prerequisites.

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