Get application

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered structurally. The description adds genuinely new behavioral context: the response includes deployment methods, and the ID is discoverable from the console URL on the application page. It does not say what happens on an unknown ID, but the additions materially exceed the annotation set.

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?

Two sentences, no filler, and the core scope is front-loaded ahead of the discoverability hint. Every clause carries distinct information.

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 single-required-parameter read tool with no output schema, the description covers what is fetched, why it matters, and how to source the ID. The only gap is return-shape detail—what 'deployment methods' look like and whether the object includes other fields—which is minor given the tool's simplicity.

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 for the single 'id' parameter. The description earns above baseline by explaining where an agent can obtain a valid ID (the Miradore console URL on the application's page), which the schema's terse "Miradore application ID." does not convey.

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 ("Get an application from the Miradore application catalog by its ID") plus the returned payload (deployment methods). It is clearly distinguishable from list_config_profiles, deploy_application, and the other device/user siblings because it names the catalog and the lookup key.

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 parenthetical "(needed for deploy_application)" gives an explicit downstream-use condition, which is strong when-to-use guidance. It stops short of when-not guidance (e.g., use a catalog list tool to find IDs you don't already have), so it is clear context without full routing.

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