ise_ers_get_ldap

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It's a read operation (get), but the description doesn't state what happens if the ID doesn't exist, whether deployment targeting requires the deployment param, or any default behavior. It adds minimal behavioral context beyond the fact that it retrieves a single object. There is no contradiction with annotations since none exist.

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 efficient sentence with zero wasted words. It names the tool's function clearly and compactly. Nothing extraneous is included.

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 single-object get operation with only 2 parameters (one required), the description is reasonably adequate. However, without annotations and no output schema, it could add value by noting error behavior or typical response structure. The deployment parameter is well-documented in the schema, which contributes to completeness. Overall it's adequate but leaves some behavioral gaps around error handling and the undocumented id parameter.

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 50% - the id parameter is undocumented in the schema while deployment is well-described. The description itself identifies 'id' as the lookup key ('by ID') which adds some meaning. However, with one parameter completely undocumented in both schema and description, the tool doesn't fully compensate. The description adds the crucial semantic that 'id' is the object identifier for lookup.

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 'Get a single LDAP Identity Sources object by ID' clearly states the verb (get), the resource (LDAP Identity Sources object), and the selection mechanism (by ID). It distinguishes from siblings like ise_ers_search_ldap and ise_ers_list_ldap through the explicit 'by ID' qualifier. It's concise and specific, though it doesn't mention the deployment parameter dimension.

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 a use case (fetching one specific LDAP identity source when you know its ID) but doesn't explicitly contrast with the 'search' variant for when you don't know the ID, nor does it note when to use list vs get. The schema's deployment parameter does provide context on targeting specific deployments, but no exclusions or alternatives are stated in the description itself.

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