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 valuable non-structural context — the hosting split and the caveat that valuations are unverified author declarations — but says nothing about ordering, pagination, or return shape.

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 tight sentences with no waste, and the core resource statement is front-loaded ahead of the hosting and valuation caveats. Slightly under-specified rather than verbose, but structurally sound.

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?

With no output schema, the description would ideally hint at what an app record contains; it instead covers hosting and valuation caveats only. For a simple read-only list tool with annotations carrying the safety profile, this is adequate but leaves the 'limit' parameter and return contents unexplained.

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 only 50%: 'repo' is documented in the schema, but 'limit' is undocumented in both schema and description. The description does not compensate for this gap or add any filtering/pagination semantics.

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 identifies the resource clearly — applications built by the network — and adds useful scoping detail about where apps are hosted (/app/<slug> vs. elsewhere). It lacks an explicit action verb (list/retrieve), so the operation must be inferred, and it does not distinguish itself from the singular sibling project100_app.

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?

There is no statement of when to use this tool versus project100_app or the other app-related siblings, and no prerequisites or context cues are given. The agent is left to infer that this is the plural/list variant purely from the name.

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