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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds two genuinely new behavioral facts: results are single-page and continuation must go through a next token that preserves filters, plus a required PORTFOLIOS read permission. It stops short of describing default ordering or what an empty/deactivated portfolio looks like.

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?

Three short sentences, zero padding, with the core action first and the pagination and permission constraints immediately after. Every sentence adds information an agent needs.

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 7-parameter tool with no output schema and no annotation coverage of filtering behavior, the description leaves the entire query surface undocumented. An agent knows it lists portfolios one page at a time but not how to filter, sort, or interpret the results.

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 0% across 7 parameters, so the description carries the full burden and largely fails: name, orderby, includeDeactivated, and the two lastModifiedDateTime bounds get no explanation of format or semantics. Only the existence of "filters" is hinted at via the pagination sentence.

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?

States a specific verb and resource ("List Propertyware portfolios"), which cleanly distinguishes it from the singular sibling propertyware_get_portfolio. It does not name siblings explicitly, but the list/get split is unambiguous from the names alone.

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?

"One page; use next (preserves filters) for the following call" gives real guidance on pagination continuation, and the permission line sets a prerequisite. However, it never says when to use this versus propertyware_get_portfolio, nor when to reach for filters like includeDeactivated or the lastModifiedDateTime range.

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