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

The readOnlyHint annotation already declares the safety profile, so the trailing 'Read-only' is largely redundant. The description does add value by naming the fields returned (name, repository, branch, state, pipeline summary), which is context the annotations cannot provide, but it says nothing about pagination envelope or result limits.

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, front-loaded with the resource and its scope before parameters. The final 'Read-only' clause duplicates the annotation and is the only real waste.

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 usefully compensates by listing the fields an application record contains. For a simple paginated read tool this is largely complete, though it could mention the paging envelope or default page size.

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 all three parameters are fully documented in the schema itself. The description only gestures at 'search filter and pagination' without adding format, semantics, or defaults beyond what the schema already states, which is the expected baseline 3.

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 the organisation's Applications) and even defines the resource as source-repo-backed deliverables with CI/CD pipelines, then enumerates the returned fields. This is enough to distinguish it from the singular get_application, though it never explicitly names related siblings such as list_application_demos or list_application_workflow_runs.

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?

The description offers no when-to-use or when-not-to-use guidance and names no alternatives. 'Optional search filter and pagination' describes the parameters rather than the situations that should route an agent here instead of get_application or the application-specific list tools.

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