List tool apps needing attention

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds the HTTP method (GET) and endpoint path, plus authorization class. This provides useful context beyond annotations but does not disclose any additional behavioral traits like pagination, filtering, or what 'attention' means.

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 concise: two sentences capturing the purpose, HTTP method, and authorization. Every word earns its place. There is no fluff, and it is front-loaded with the core action.

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 simple list tool with one parameter and an output schema (so return values are documented), the description is minimally adequate. It covers the what (list) and the resource (tool apps needing attention). However, it omits context like what qualifies as 'needing attention' or how to 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?

There is only one parameter (companyId in path), but schema description coverage is 0%. The description does not explain what companyId represents or any constraints on it. With low coverage, the description should compensate, but it provides no parameter semantics beyond the endpoint path.

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 states 'List tool apps needing attention', which is a specific verb+resource combination. It clearly indicates the tool returns a list of tool apps requiring attention. However, it does not differentiate from the sibling tool 'pc_get_companies_by_company_id_attention', which might also list attention items. The purpose is clear but lacks sibling distinction.

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 is provided on when to use this tool versus alternatives. For example, there is no mention of when to use this instead of 'pc_get_companies_by_company_id_attention' or other list tools. Context signals and sibling list are available, but the description itself offers no usage direction.

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