get-experience

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, the description is a simple read operation ('Get...') with no parameters, and there are no side effects to disclose. For a zero-parameter getter, there is little behavioral context needed beyond what the verb implies. A moderate score is appropriate since it's a read operation with no caveats needed.

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, short sentence with no wasted words. It hits the essential purpose with minimal overhead. However, it is under-specified relative to its sibling context, slightly conflating conciseness with brevity.

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 zero parameters, no output schema, and no annotations, the description is all there is. For a simple getter, 'Get Priya Gautam's professional experience' covers the essentials, but given the existence of siblings like search-priya-profile and search-profile, the description could clarify what is included/excluded in 'professional experience' versus what skills/projects/education tools cover. There's ambiguity about the scope of the returned content.

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?

The tool has 0 parameters and schema description coverage is 100%, so there are no parameters that require documentation. Per the rubric, 0 parameters = baseline 4. The description extracts 'Priya Gautam's' specific experience, which adds the only contextual meaning possible for a parameterless tool.

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 verb 'Get' plus resource 'Priya Gautam's professional experience' clearly states what the tool does. However, among siblings like get-skills, get-projects, and get-education, it's implied that this returns the experience section specifically, but the description does not explicitly differentiate what 'professional experience' encompasses versus what siblings return.

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 provides no guidance on when to use this tool versus alternatives. Among siblings like get-profile, search-priya-profile, and search-profile, there is no indication of when a user should pick get-experience, search tools, or other getters. No when/when-not guidance is provided.

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