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

Annotations already declare readOnlyHint and destructiveHint false, so safety is covered. The description adds genuinely new context beyond them: a sign-in requirement ('like every tool that touches an app'), the fact that app names can collide and app_id disambiguates, and the exact behavior when organization is omitted.

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?

Front-loaded with the action and result, then conditions, then edge cases. Slightly dense in the final sentence, but every clause carries operational information (auth, disambiguation, organization scoping).

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?

An output schema exists, so return values need no explanation. The description covers auth, scope defaults, and the name-collision caveat. Minor gap: no explicit statement of whether the list is paginated or ordered.

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%, so the baseline is 3. The description goes beyond the schema's 'which organization to list; omit to see your personal apps' by explaining what happens to other organizations you belong to when the parameter is omitted, which is real added value.

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 plus the payload (URL and status), which is more informative than a bare 'list apps'. It does not explicitly distinguish itself from near-siblings such as get_app_status or get_app_context, so it stops short of a 5.

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?

Gives clear triggering conditions: 'For when the person asks what they have, or when you need an app_id you are not already holding.' That second clause implicitly routes callers elsewhere when they already have an app_id, but no sibling is named as the alternative.

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