create_portal_page

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

Annotations already indicate readOnlyHint=false (not read-only) and destructiveHint=false, so the agent knows it's a mutation without destruction. The description adds the precondition 'requires WRITE_ENABLED=true', which is valuable beyond annotations. However, it does not disclose return behavior, error cases, or side effects.

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 a single sentence that front-loads the core action and includes a key requirement. It is concise and contains no unnecessary information. However, it could be slightly expanded to include more usage guidance without loss of conciseness.

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?

Despite having annotations and a high schema coverage, the description is very brief. For a creation tool with no output schema, it lacks information about the return value, confirmation of success, or any side effects. The agent has insufficient context to fully understand the tool's behavior.

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%, with all parameters described in the schema. The description does not add any additional meaning to the parameters beyond what the schema provides. Thus, it meets the baseline but does not enhance understanding.

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 action 'Create a new page inside a Service Portal', specifying the verb 'Create' and the resource 'page inside a Service Portal'. It distinguishes from sibling tools like create_portal (creates the portal itself) and create_portal_widget (creates widgets). The requirement 'WRITE_ENABLED=true' adds specificity.

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 mentions a prerequisite (WRITE_ENABLED=true), which guides when the tool can be used. However, it does not explicitly state when to use this tool versus alternatives like create_portal or create_portal_widget, nor does it provide exclusions or context about what the created page is used for.

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