deployado_current_deployment

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world profile, so the safety story is fully covered by structured data. The description adds essentially no behavioral context beyond that — nothing about what happens when no deployment is active, or about permissions — which is adequate but minimal for a trivial read.

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?

One short sentence that front-loads the verb and the resource, with zero filler. Nothing redundant and nothing that could be trimmed.

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-parameter read tool with rich annotations and no output schema, the description is nearly sufficient — the resource and scope are clear. The only gap is edge-case behavior (no active deployment) and how it relates to the get_deployment sibling, which prevents a 5.

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 description coverage is 100% ('App ID (UUID)'), so the single parameter is fully documented by the schema. The description contributes no additional parameter semantics such as format quirks or ID sources, so the baseline 3 applies.

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 the currently active deployment') with a clear scope ('for an app'), which is more precise than a generic list or get. It does not distinguish itself from close siblings like deployado_get_deployment (likely fetch-by-ID) or deployado_list_deployments, so the agent must infer which to pick.

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?

Usage is only implied by the word 'currently active' — the agent can infer this is for finding the live deployment, but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_deployment or list_deployments.

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