list_portals

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

No annotations are provided, so the description carries the full burden. It mentions the OAuth prerequisite, which is a behavioral precondition, but does not disclose whether the operation is read-only, what side effects (if any) exist, or how the results are returned. The existence of sibling 'list_selected_portals' suggests a distinction, but this description does not clarify that it lists all portals versus selected ones. With zero annotation support, this is a significant gap.

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 short sentences with zero fluff. The action and resource are front-loaded, and the prerequisite is stated succinctly. Every word earns its place.

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?

For a zero-parameter list tool with no output schema, the description covers the core purpose and a key prerequisite. It could add that the operation is read-only or specify the return format, but those are minor given the simplicity. The scope ('available to this account') adds useful context. It is mostly complete, though a note on output would be ideal.

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?

There are no parameters (0 params), so the schema is trivially covered. The description does not need to add parameter-specific details. Per the guidelines, with 0 params the baseline is 4, and there is nothing else to add.

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 (List) and the specific resource (Zoho portals) and scopes it to 'this account'. It distinguishes itself from sibling tools like list_projects and list_users by naming the resource type. The verb 'List' is explicit and unambiguous.

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?

It provides a clear prerequisite ('Requires configure_oauth first'), which tells the agent the setup needed before calling. However, it does not explicitly contrast with alternative listing tools or state when not to use it, though the resource specificity makes the usage context clear. It gives a necessary condition but not explicit exclusions.

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