get-rum-application

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

The description adds the phrase 'detailed information' beyond the annotations 'readOnlyHint' and 'openWorldHint', but does not provide additional behavioral traits like response structure or pagination. Annotations already cover the safety profile.

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?

The description is a single, front-loaded sentence with no redundant words. It is appropriately concise.

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 simple read tool with one parameter and no output schema, the description adequately covers the basics. It could expand on what 'detailed information' includes, but the simplicity limits the need.

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% and the schema already describes the 'id' parameter as 'RUM application ID'. The description adds no new semantic detail beyond restating that the tool retrieves by ID.

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 clearly specifies the action 'Get', the resource 'RUM application', and the identifier 'by ID'. It distinguishes from sibling tools like 'list-rum-applications' which retrieves all applications.

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 implies usage when you have a specific ID, but does not explicitly mention alternatives like 'list-rum-applications' for when you need all applications.

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