update_portal_to_account

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

With no annotations, description must disclose behavior. Merely stating 'Update' without details on side effects, idempotency, or what fields change leaves significant gaps. The tool name implies a connection to an account, but this is not explained.

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?

Extremely short phrase lacks substantive content required for a useful tool description. Conciseness is achieved at the expense of completeness and clarity.

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 no output schema and no annotations, the description should provide richer context (e.g., what attributes are updatable, return format, etc.). Currently it is too minimal for an AI agent to use correctly.

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?

No parameters exist, so baseline 4 applies. The description could clarify that no parameters are needed (or why), but the absence is acceptable. The empty schema fully covers the parameter space.

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 'Update a portal' is a tautology that restates the tool name without clarifying what 'portal' refers to or how it relates to 'account'. It fails to distinguish from sibling tools like 'add_new_portal_to_account' or 'get_portal'.

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 on when to use this tool versus alternatives. No context about prerequisites, required state (e.g., portal must exist), or when to prefer creation vs update.

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