create_dynamic_page_row_featured

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It merely restates that it 'creates' the object, which is inherent in the name, and omits any side effects, authentication needs, expected parent relationship, or response behavior. This provides no additional 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 brief but this is under-specification, not effective conciseness. It conveys no information beyond the tool name, so it does not earn its place as a useful description.

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 handles authentication tokens, a parent row URL, and a nested feat_data object, and there is no output schema. The description provides no operational context, expected behavior, or relationship to sibling tools, making it severely incomplete.

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 only 25%, with api_url the only described parameter. The description itself does not mention any parameters, leaving feat_data (a complex nested object), token, and cookie entirely unexplained. It fails to compensate for the low 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?

The description clearly states the tool creates a DynamicPageRowFeatured in Plone, using a specific verb and resource. However, it does not differentiate from the sibling tool create_dynamic_page_row, leaving ambiguity about what 'featured' specifically means.

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 guidance on when to use this tool versus alternatives like create_dynamic_page_row or create_content. It lacks any context on prerequisites, scenarios, or exclusions, so the agent must rely on the name alone.

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